Access scaling plans using interface VPC endpoints

You can use AWS PrivateLink to create a private connection between your VPC and AWS Auto Scaling. You can access AWS Auto Scaling as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Auto Scaling.

You establish this private connection by creating an interface endpoint, powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for AWS Auto Scaling.

For more information, see Access AWS services through AWS PrivateLink in the AWS PrivateLink Guide.

Create an interface VPC endpoint for scaling plans

Create an endpoint for AWS Auto Scaling scaling plans using the following service name:

com.amazonaws.region.autoscaling-plans

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. AWS Auto Scaling API calls other AWS services using either service endpoints or private interface VPC endpoints, whichever are in use.

Create a VPC endpoint policy for scaling plans

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

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

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

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

Endpoint migration

On November 22, 2019, we introduced autoscaling-plans.region.amazonaws.com as the new default DNS hostname and endpoint for calls to the AWS 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.

Endpoint to Call When Using the CLI or the AWS Auto Scaling API

For the current release of AWS Auto Scaling, your calls to the AWS Auto Scaling API automatically go to the autoscaling-plans.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://autoscaling-plans.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.