AWS elasticbeanstalk documentation change
Summary
Updated documentation to clarify migration from launch configurations to launch templates, adjusted failure conditions related to custom policies during environment updates (instead of spot instance enablement), and revised linked resource titles.
Security assessment
The changes focus on migration procedures and permissions requirements for launch templates. While permissions are security-adjacent, there is no evidence of a specific security vulnerability being addressed. The updates refine operational guidance rather than introduce or mitigate security flaws.
Diff
diff --git a/elasticbeanstalk/latest/dg/command-options-general.md b/elasticbeanstalk/latest/dg/command-options-general.md index e68654ba9..aef5cf6e9 100644 --- a//elasticbeanstalk/latest/dg/command-options-general.md +++ b//elasticbeanstalk/latest/dg/command-options-general.md @@ -127 +127 @@ For more information, see [Configuring the instance metadata service](https://do -This 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). | `false` – platforms based on Windows server, Amazon Linux 2 and earlier `true` – platforms based on Amazon Linux 2023 | `true` `false` +This 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). | `false` – platforms based on Windows server, Amazon Linux 2 and earlier `true` – platforms based on Amazon Linux 2023 | `true` `false` @@ -208 +208 @@ BlockDeviceMappings | Attach additional Amazon EBS volumes or instance store vo -This 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). When mapping instance store volumes, you only need to map the device name to a volume name. However, we recommend, when mapping Amazon EBS volumes, you additionally specify some or all of the following fields (each field must be separated by a colon): +This 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). When mapping instance store volumes, you only need to map the device name to a volume name. However, we recommend, when mapping Amazon EBS volumes, you additionally specify some or all of the following fields (each field must be separated by a colon): @@ -227 +227 @@ RootVolumeType | Volume type (magnetic, general purpose SSD or provisioned IOPS -This 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). | Varies by platform. | `standard` for magnetic storage. `gp2` or `gp3` for general purpose SSD. `io1` for provisioned IOPS SSD. +This 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). | Varies by platform. | `standard` for magnetic storage. `gp2` or `gp3` for general purpose SSD. `io1` for provisioned IOPS SSD. @@ -312 +312 @@ EnableSpot | Enable Spot Instance requests for your environment. When `false`, -This 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). | `false` | `true` `false` +This 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). | `false` | `true` `false`