AWS elasticbeanstalk documentation change
Summary
Updated RootVolumeType documentation to clarify migration to launch templates
Security assessment
Change focuses on volume type configuration migration process, not security-related content.
Diff
diff --git a/elasticbeanstalk/latest/dg/using-features.managing.ec2.console.md b/elasticbeanstalk/latest/dg/using-features.managing.ec2.console.md index 009ff2cdf..6ca7bd108 100644 --- a//elasticbeanstalk/latest/dg/using-features.managing.ec2.console.md +++ b//elasticbeanstalk/latest/dg/using-features.managing.ec2.console.md @@ -92 +92 @@ You can modify **Root volume type** to use magnetic storage or provisioned IOPS -The `RootVolumeType` 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 `RootVolumeType` 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).