AWS elasticbeanstalk documentation change
Summary
Clarified that enabling Spot Instances triggers migration to launch templates for existing environments, updated failure scenario wording, and adjusted linked documentation title.
Security assessment
The changes focus on operational aspects of environment migration to launch templates and permission requirements during updates. While permissions are mentioned, there is no evidence of addressing a specific security vulnerability or weakness. The update refines existing documentation rather than introducing new security controls.
Diff
diff --git a/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-enable-spot.md b/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-enable-spot.md index 750260a97..dd2ac3cb9 100644 --- a//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-enable-spot.md +++ b//elasticbeanstalk/latest/dg/environments-cfg-autoscaling-enable-spot.md @@ -19 +19 @@ For more detailed information about Spot Instances, including explanation of key -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).