You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have identified that one or more of your accounts uses Amazon EC2 Auto Scaling launch configurations. After December 31, 2022 no new Amazon Elastic Compute Cloud (Amazon EC2) instance types will be added to launch configurations. After this date, existing launch configurations will continue to work, but new EC2 instances will only be supported through launch templates.
In 2021, through email notifications, console banners, documentation updates, re:Post banners, and a blog post [1], AWS announced that Amazon EC2 Auto Scaling would stop adding new EC2 instance types to launch configurations [2] by the end of 2022. Launch templates [3] exceed launch configurations in functionality. In addition to supporting all new EC2 instance types, launch templates provides a simple way to combine multiple instance types and purchase options, configure instance networking settings, use these settings with other AWS services, and maintain versions of these settings. You can convert your launch configurations to launch templates using the AWS Management Console [4].
The following are key dates for launch configuration deprecation:
December 31, 2022
No new EC2 features or new EC2 instance types will be added to launch configurations after this date.
March 31, 2023
New accounts created after this date will not be able to create new launch configurations via the console. API and CLI access will remain available to support customers with automation use cases.
December 31, 2023
New accounts created after this date will not be able to create new launch configurations.
Existing launch configuration features will continue to function.
To find your affected resources, please execute the following using Cloudshell:
Access an AWS CloudShell Environment in any region where it is supported
Copy inventory.py to your local environment by executing the following command
Execute the following script - being sure to use the "-i" argument, which will list both the Auto Scaling group and the launch configuration, and for a CloudShell environment you should use the -r ROLE_ARN argument to specify a role to assume as the script currently does not support CloudShell's inherited credentials
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
As received from Amazon:
Hello,
We have identified that one or more of your accounts uses Amazon EC2 Auto Scaling launch configurations. After December 31, 2022 no new Amazon Elastic Compute Cloud (Amazon EC2) instance types will be added to launch configurations. After this date, existing launch configurations will continue to work, but new EC2 instances will only be supported through launch templates.
In 2021, through email notifications, console banners, documentation updates, re:Post banners, and a blog post [1], AWS announced that Amazon EC2 Auto Scaling would stop adding new EC2 instance types to launch configurations [2] by the end of 2022. Launch templates [3] exceed launch configurations in functionality. In addition to supporting all new EC2 instance types, launch templates provides a simple way to combine multiple instance types and purchase options, configure instance networking settings, use these settings with other AWS services, and maintain versions of these settings. You can convert your launch configurations to launch templates using the AWS Management Console [4].
The following are key dates for launch configuration deprecation:
December 31, 2022
March 31, 2023
December 31, 2023
Existing launch configuration features will continue to function.
To find your affected resources, please execute the following using Cloudshell:
Access an AWS CloudShell Environment in any region where it is supported
Copy inventory.py to your local environment by executing the following command
"curl -O https://raw.githubusercontent.com/aws-samples/amazon-ec2-auto-scaling-group-examples/main/tools/launch-configuration-inventory/inventory.py"
"python3 inventory.py -i -r arn:aws:iam::[ACCOUNT_ID]:role/[ROLE_NAME]"
If you are unable to move to launch templates due to lack of tooling or functionalities or have any concerns, please contact the AWS Support Team [5].
[1] https://aws.amazon.com/blogs/compute/amazon-ec2-auto-scaling-will-no-longer-add-support-for-new-ec2-features-to-launch-configurations/
[2] https://docs.aws.amazon.com/autoscaling/ec2/userguide/LaunchConfiguration.html
[3] https://docs.aws.amazon.com/autoscaling/ec2/userguide/LaunchTemplates.html
[4] https://console.aws.amazon.com/ec2/v2/home?#LaunchConfigurations
[5] https://aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:global::event/AUTOSCALING/AWS_AUTOSCALING_OPERATIONAL_NOTIFICATION/AWS_AUTOSCALING_OPERATIONAL_NOTIFICATION_08b3a84bdea508c769ba672a190b778dafe7a6dde46101f76c3d4d7ef0c2ee1a&eventTab=details
The text was updated successfully, but these errors were encountered: