AWS elasticbeanstalk documentation change
Summary
Updated documentation to clarify that EnableSpot triggers migration to launch templates (not creation) and updated link title to 'Migrating...'
Security assessment
Change focuses on migration process and permission requirements for launch templates, not security vulnerabilities or features.
Diff
diff --git a/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-spot-and-demand.md b/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-spot-and-demand.md index 977e16f94..88a16d76a 100644 --- a//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-spot-and-demand.md +++ b//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-spot-and-demand.md @@ -35 +35 @@ The previously listed options correlate with the following options in the [aws:a -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).