Application Auto Scaling and interface VPC endpoints - Application Auto Scaling

Application Auto Scaling and interface VPC endpoints

You can improve the security posture of your VPC by configuring Application Auto Scaling to use an interface VPC endpoint. Interface endpoints are powered by AWS PrivateLink, a technology that enables you to privately access Application Auto Scaling APIs by restricting all network traffic between your VPC and Application Auto Scaling to the Amazon network. With interface endpoints, you also don't need an internet gateway, a NAT device, or a virtual private gateway.

You are not required to configure AWS PrivateLink, but it's recommended. For more information about AWS PrivateLink and VPC endpoints, see What is AWS PrivateLink? in the AWS PrivateLink Guide.

Create an interface VPC endpoint

Create an endpoint for Application Auto Scaling using the following service name:

com.amazonaws.region.application-autoscaling

For more information, see Access an AWS service using an interface VPC endpoint in the AWS PrivateLink Guide.

You do not need to change any other settings. Application Auto Scaling calls other AWS services using either service endpoints or private interface VPC endpoints, whichever are in use.

Create a VPC endpoint policy

You can attach a policy to your VPC endpoint to control access to the Application Auto Scaling API. The policy specifies:

  • The principal that can perform actions.

  • The actions that can be performed.

  • The resource on which the actions can be performed.

The following example shows a VPC endpoint policy that denies everyone permission to delete a scaling policy through the endpoint. The example policy also grants everyone permission to perform all other actions.

{ "Statement": [ { "Action": "*", "Effect": "Allow", "Resource": "*", "Principal": "*" }, { "Action": "application-autoscaling:DeleteScalingPolicy", "Effect": "Deny", "Resource": "*", "Principal": "*" } ] }

For more information, see VPC endpoint policies in the AWS PrivateLink Guide.

Endpoint migration

Application Auto Scaling recently introduced application-autoscaling.region.amazonaws.com as the new default DNS hostname and endpoint for calls to the Application Auto Scaling API. The new endpoint is compatible with the latest release of the AWS CLI and SDKs. If you have not done so already, install the latest AWS CLI and SDKs to use the new endpoint. To update the AWS CLI, see Installing the AWS CLI using pip in the AWS Command Line Interface User Guide. For information about the AWS SDKs, see Tools for Amazon Web Services.

Note

For backward compatibility, the autoscaling.region.amazonaws.com endpoint will continue to be supported for calls to the Application Auto Scaling API. To set up the autoscaling.region.amazonaws.com endpoint as a private interface VPC endpoint, see Amazon EC2 Auto Scaling and interface VPC endpoints in the Amazon EC2 Auto Scaling User Guide.

Endpoint to Call When Using the CLI or the AWS API

For the current release of Application Auto Scaling, your calls to the Application Auto Scaling API automatically go to the application-autoscaling.region.amazonaws.com endpoint instead of autoscaling.region.amazonaws.com.

You can call the new endpoint in the CLI by using the following parameter with each command to specify the endpoint: --endpoint-url https://application-autoscaling.region.amazonaws.com.

Although it is not recommended, you can also call the old endpoint in the CLI by using the following parameter with each command to specify the endpoint: --endpoint-url https://autoscaling.region.amazonaws.com.

For the various SDKs used to call the APIs, see the documentation for the SDK of interest to learn how to direct the requests to a specific endpoint. For more information, see Tools for Amazon Web Services.