AWS elasticbeanstalk documentation change
Summary
Updated DisableIMDSv1 documentation to clarify migration process to launch templates (twice in file)
Security assessment
While DisableIMDSv1 relates to security, the change only addresses migration mechanics rather than security functionality itself.
Diff
diff --git a/elasticbeanstalk/latest/dg/environments-cfg-ec2-imds.md b/elasticbeanstalk/latest/dg/environments-cfg-ec2-imds.md index 7fea311cf..4dd72d2a1 100644 --- a//elasticbeanstalk/latest/dg/environments-cfg-ec2-imds.md +++ b//elasticbeanstalk/latest/dg/environments-cfg-ec2-imds.md @@ -51 +51 @@ You can modify your Elastic Beanstalk environment's Amazon EC2 instance configur -The `DisableIMDSv1` 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 `DisableIMDSv1` 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). @@ -76 +76 @@ You can use a [configuration option](./command-options.html) in the `[aws:autosc -The `DisableIMDSv1` 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 `DisableIMDSv1` 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).