AWS elasticbeanstalk documentation change
Summary
Updated documentation to emphasize migration from launch configurations to launch templates, clarified deprecation timeline, added benefits of launch templates, simplified migration instructions, and updated permissions requirements.
Security assessment
The changes focus on operational migration guidance and feature deprecation notices rather than addressing security vulnerabilities or introducing security features. No security-related terminology, CVEs, or explicit security controls are mentioned in the diff.
Diff
diff --git a/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-launch-templates.md b/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-launch-templates.md index 659a84b1a..433cf6288 100644 --- a//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-launch-templates.md +++ b//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-launch-templates.md @@ -5 +5 @@ -Option settingsCheck for launch configurationRequired permissionsMore information +onceOption settingsCheck for launch configurationRequired permissionsMore information @@ -7 +7 @@ Option settingsCheck for launch configurationRequired permissionsMore informatio -# Launch templates for your Elastic Beanstalk environment +# Migrating your Elastic Beanstalk environment to launch templates @@ -9 +9 @@ Option settingsCheck for launch configurationRequired permissionsMore informatio -This topic explains that AWS is phasing out _launch configurations_ and replacing them with _launch templates_. It also explains how Elastic Beanstalk environments are affected. If you'd like to migrate an older environment, that was created prior to October 1, 2024, from launch configurations to launch templates follow the instructions in this topic. +As of October 1, 2024, Amazon EC2 Auto Scaling no longer supports launch configurations for new accounts. Accounts created prior to that date might have launch configurations. @@ -11 +11 @@ This topic explains that AWS is phasing out _launch configurations_ and replacin -As of October 1, 2024, Amazon EC2 Auto Scaling no longer supports the creation of launch configurations for new accounts. This change is due to launch configurations being phased out and replaced by launch templates by the Amazon EC2 Auto Scaling service. For more information, see [Auto Scaling launch configurations](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html) in the _Amazon EC2 Auto Scaling User Guide_. +We recommend migrating to **launch templates** for the following benefits: @@ -13 +13 @@ As of October 1, 2024, Amazon EC2 Auto Scaling no longer supports the creation o -The transition to launch templates affects Elastic Beanstalk accounts and environments as follows: + * Improved availability for your applications @@ -15 +15 @@ The transition to launch templates affects Elastic Beanstalk accounts and enviro - * Existing environments – Existing environments that were created prior to October 1, 2024 are not impacted by the launch configuration deprecation. However, if you'd like to migrate your existing environment to launch templates, use the configuration option settings listed in Option settings for launch templates. + * Better optimization of workloads in your Auto Scaling groups @@ -17 +17 @@ The transition to launch templates affects Elastic Beanstalk accounts and enviro - * New accounts – New Accounts will automatically use launch templates by default, since launch configurations are deprecated. + * Access to the latest EC2 and Auto Scaling features @@ -19 +18,0 @@ The transition to launch templates affects Elastic Beanstalk accounts and enviro - * Existing accounts – Existing accounts are not impacted by the launch configuration deprecation. However, if you'd like to migrate any of your existing environments with launch configurations to launch templates, use the configuration option settings listed in Option settings for launch templates. @@ -22,0 +22 @@ The transition to launch templates affects Elastic Beanstalk accounts and enviro +For more information, see [Auto Scaling launch configurations](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html) in the _Amazon EC2 Auto Scaling User Guide_. @@ -26 +26 @@ The transition to launch templates affects Elastic Beanstalk accounts and enviro -Select at least one of the option settings in the following list to direct Elastic Beanstalk to create an environment with a launch template. If you already have existing environments based on launch configurations, select at least one of these options to move an already existing environment from a launch configuration to a launch template. +To migrate your environment from launch configurations to launch templates, set one of the following configuration options: @@ -34 +34 @@ Select at least one of the option settings in the following list to direct Elast - * `EnableSpot` option set to **true**. For more information, see [Spot Instance support for your Elastic Beanstalk environment](./environments-cfg-autoscaling-spot.html) and [Enabling Spot Instances](./environments-cfg-autoscaling-enable-spot.html). + * `EnableSpot` option set to **true**. For more information, see [Enabling Spot Instances](./environments-cfg-autoscaling-enable-spot.html). @@ -41 +41 @@ Select at least one of the option settings in the following list to direct Elast -Once an environment is using launch templates, Elastic Beanstalk will never move it back to launch configurations. This is the case even if any these option settings that prompted the original use of launch templates are removed. +After an environment begins using launch templates, Elastic Beanstalk does not revert to launch configurations, even if you remove the configuration options that originally triggered the use of launch templates. @@ -68 +68 @@ For more information, see [View stack information](https://docs.aws.amazon.com/A -If you use our Elastic Beanstalk [managed service role policies](./iam-servicerole.html), your environment has the required permissions to create launch templates via the managed policy [AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy.html). +The default Elastic Beanstalk managed service role policy [AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy.html) provides the required permissions to create and manage launch templates. Elastic Beanstalk must manage launch templates to complete many environment operations, including creating environments. @@ -70 +70 @@ If you use our Elastic Beanstalk [managed service role policies](./iam-servicero -If you have any custom policies attached to an Elastic Beanstalk service role, you must ensure that the following permissions are available. Doing so provides Elastic Beanstalk permission to create launch templates in your account. +If you attach custom policies to an Elastic Beanstalk service role, verify that the service role includes the following permissions for creating launch templates. These permissions enable Elastic Beanstalk to successfully create and update environments in your account: @@ -120 +120 @@ To learn more about launch templates, see [Auto Scaling launch templates ](https -To learn more about the AWS transition from launch configurations to launch templates, along with the benefits that launch templates offer, see [ Amazon EC2 Auto Scaling will no longer add support for new EC2 features to Launch Configurations](https://aws.amazon.com/blogs/compute/amazon-ec2-auto-scaling-will-no-longer-add-support-for-new-ec2-features-to-launch-configurations/) in the _AWS Compute Blog_. +To learn more about the AWS transition to launch templates and the benefits they offer, see [ Amazon EC2 Auto Scaling will no longer add support for new EC2 features to Launch Configurations](https://aws.amazon.com/blogs/compute/amazon-ec2-auto-scaling-will-no-longer-add-support-for-new-ec2-features-to-launch-configurations/) in the _AWS Compute Blog_. @@ -124 +124 @@ To learn more about the AWS transition from launch configurations to launch temp -You don't need to follow the procedure that's referenced in this blog article to transition an older environment to launch templates . To migrate an existing Elastic Beanstalk environment to launch templates, you only need to set one of the options listed in Option settings for launch templates. +You don't need to follow the procedure referenced in this blog article to transition an older environment to launch templates. To migrate an existing Elastic Beanstalk environment to launch templates, set one of the options listed in Option settings for launch templates.