AWS elasticbeanstalk documentation change
Summary
Updated documentation about EnableSpot option's behavior regarding launch template migration. Changed context from environment creation/update failures when enabling spot instances to failures during general environment configuration updates. Updated link title to 'Migrating your Elastic Beanstalk environment to launch templates'.
Security assessment
The changes clarify required IAM permissions for launch template management when migrating environments, which relates to security best practices for access control. However, there is no evidence this addresses a specific security vulnerability - it primarily improves documentation about permission requirements for a configuration change.
Diff
diff --git a/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-configuration-approaches.md b/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-configuration-approaches.md index 9147c6444..a75c924be 100644 --- a//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-configuration-approaches.md +++ b//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-configuration-approaches.md @@ -13 +13 @@ This topic describes the different approaches to configure Auto Scaling capacity -The `EnableSpot` option setting can cause Elastic Beanstalk to create an environment with a launch template or update an existing environment from launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you enable spot instances for your environment. For more information and other considerations, see [Launch templates for your Elastic Beanstalk environment](./environments-cfg-autoscaling-launch-templates.html). +The `EnableSpot` option setting can cause Elastic Beanstalk to migrate an existing environment with launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you update your environment configuration. For more information and other considerations, see [Migrating your Elastic Beanstalk environment to launch templates ](./environments-cfg-autoscaling-launch-templates.html). @@ -45 +45 @@ If you use rolling updates, be sure that the maximum instance count is higher th -The `EnableSpot` option setting can cause Elastic Beanstalk to create an environment with a launch template or update an existing environment from launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you enable spot instances for your environment. For more information and other considerations, see [Launch templates for your Elastic Beanstalk environment](./environments-cfg-autoscaling-launch-templates.html). +The `EnableSpot` option setting can cause Elastic Beanstalk to migrate an existing environment with launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you update your environment configuration. For more information and other considerations, see [Migrating your Elastic Beanstalk environment to launch templates ](./environments-cfg-autoscaling-launch-templates.html). @@ -125 +125 @@ To choose Spot Instance types, use the [Spot Instance Advisor](https://aws.amazo -The `EnableSpot` option setting can cause Elastic Beanstalk to create an environment with a launch template or update an existing environment from launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you enable spot instances for your environment. For more information and other considerations, see [Launch templates for your Elastic Beanstalk environment](./environments-cfg-autoscaling-launch-templates.html). +The `EnableSpot` option setting can cause Elastic Beanstalk to migrate an existing environment with launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you update your environment configuration. For more information and other considerations, see [Migrating your Elastic Beanstalk environment to launch templates ](./environments-cfg-autoscaling-launch-templates.html). @@ -165 +165 @@ The fist option listed, `IamInstanceProfile` in the [aws:autoscaling:launchconfi -The `EnableSpot` option setting can cause Elastic Beanstalk to create an environment with a launch template or update an existing environment from launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you enable spot instances for your environment. For more information and other considerations, see [Launch templates for your Elastic Beanstalk environment](./environments-cfg-autoscaling-launch-templates.html). +The `EnableSpot` option setting can cause Elastic Beanstalk to migrate an existing environment with launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you update your environment configuration. For more information and other considerations, see [Migrating your Elastic Beanstalk environment to launch templates ](./environments-cfg-autoscaling-launch-templates.html). @@ -260 +260 @@ Enables Spot Instance requests for your environment. -The `enable-spot` option setting can cause Elastic Beanstalk to create an environment with a launch template or update an existing environment from launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you enable spot instances for your environment. For more information and other considerations, see [Launch templates for your Elastic Beanstalk environment](./environments-cfg-autoscaling-launch-templates.html). +The `enable-spot` option setting can cause Elastic Beanstalk to migrate an existing environment with launch configurations to launch templates. Doing so requires the necessary permissions to manage launch templates. These permissions are included in our managed policy. If you use custom policies instead of our managed policies, environment creation or updates might fail when you update your environment configuration. For more information and other considerations, see [Migrating your Elastic Beanstalk environment to launch templates ](./environments-cfg-autoscaling-launch-templates.html).