AWS autoscaling documentation change
Summary
Updated documentation to consistently use 'Amazon EC2 Auto Scaling group' terminology instead of 'Auto Scaling group' throughout the file. Added Amazon EC2 qualifier to service names and updated cross-reference links accordingly.
Security assessment
The changes are purely stylistic/naming convention updates to align with branding guidelines. No new security features are documented, and existing security-related content (IMDSv2 references) remains unchanged except for service name formatting. The IMDSv2 mention references existing security documentation but does not introduce new security guidance.
Diff
diff --git a/autoscaling/ec2/userguide/create-launch-config.md b/autoscaling/ec2/userguide/create-launch-config.md index 709838c5e..9508f1ed2 100644 --- a//autoscaling/ec2/userguide/create-launch-config.md +++ b//autoscaling/ec2/userguide/create-launch-config.md @@ -22 +22 @@ Limitations: -Migrate to launch templates to make sure that you don’t need to create new launch configurations now or in the future. For information about migrating your Auto Scaling groups to launch templates, see [Migrate your Auto Scaling groups to launch templates](./migrate-to-launch-templates.html). +Migrate to launch templates to make sure that you don’t need to create new launch configurations now or in the future. For information about migrating your Amazon EC2 Auto Scaling groups to launch templates, see [Migrate your Amazon EC2 Auto Scaling groups to launch templates](./migrate-to-launch-templates.html). @@ -32 +32 @@ After you create a launch configuration, you cannot modify it. Instead, you must -To associate a new launch configuration with an existing Auto Scaling group, see [Change the launch configuration for an Auto Scaling group](./change-launch-config.html). To create a new Auto Scaling group, see [Create an Auto Scaling group using a launch configuration](./create-asg-launch-configuration.html). +To associate a new launch configuration with an existing Amazon EC2 Auto Scaling group, see [Change the launch configuration for an Amazon EC2 Auto Scaling group](./change-launch-config.html). To create a new Amazon EC2 Auto Scaling group, see [Create an Amazon EC2 Auto Scaling group using a launch configuration](./create-asg-launch-configuration.html). @@ -81 +81 @@ Spot Instances are a cost-effective choice compared to On-Demand Instances, if y - 3. (Optional) For **Monitoring** , choose whether to enable the instances to publish metric data at 1-minute intervals to Amazon CloudWatch by enabling detailed monitoring. Additional charges apply. For more information, see [Configure monitoring for Auto Scaling instances](./enable-as-instance-metrics.html). + 3. (Optional) For **Monitoring** , choose whether to enable the instances to publish metric data at 1-minute intervals to Amazon CloudWatch by enabling detailed monitoring. Additional charges apply. For more information, see [Configure monitoring for Amazon EC2 Auto Scaling instances](./enable-as-instance-metrics.html). @@ -136 +136 @@ You can use one of the following commands: -Amazon EC2 Auto Scaling supports configuring the Instance Metadata Service (IMDS) in launch configurations. This gives you the option of using launch configurations to configure the Amazon EC2 instances in your Auto Scaling groups to require Instance Metadata Service Version 2 (IMDSv2), which is a session-oriented method for requesting instance metadata. For details about IMDSv2's advantages, see this article on the AWS Blog about [enhancements to add defense in depth to the EC2 instance metadata service](https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/). +Amazon EC2 Auto Scaling supports configuring the Instance Metadata Service (IMDS) in launch configurations. This gives you the option of using launch configurations to configure the Amazon EC2 instances in your Amazon EC2 Auto Scaling groups to require Instance Metadata Service Version 2 (IMDSv2), which is a session-oriented method for requesting instance metadata. For details about IMDSv2's advantages, see this article on the AWS Blog about [enhancements to add defense in depth to the EC2 instance metadata service](https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/). @@ -153 +153 @@ You can find more details on configuring the Instance Metadata Service in the fo -Use the following procedure to configure IMDS options in a launch configuration. After you create your launch configuration, you can associate it with your Auto Scaling group. If you associate the launch configuration with an existing Auto Scaling group, the existing launch configuration is disassociated from the Auto Scaling group, and existing instances will require replacement to use the IMDS options that you specified in the new launch configuration. For more information, see [Change the launch configuration for an Auto Scaling group](./change-launch-config.html). +Use the following procedure to configure IMDS options in a launch configuration. After you create your launch configuration, you can associate it with your Amazon EC2 Auto Scaling group. If you associate the launch configuration with an existing Amazon EC2 Auto Scaling group, the existing launch configuration is disassociated from the Amazon EC2 Auto Scaling group, and existing instances will require replacement to use the IMDS options that you specified in the new launch configuration. For more information, see [Change the launch configuration for an Amazon EC2 Auto Scaling group](./change-launch-config.html). @@ -214 +214 @@ When you create a launch configuration using a running instance, you can overrid -If the specified instance has properties that are not currently supported by launch configurations, the instances launched by the Auto Scaling group might not be identical to the original EC2 instance. +If the specified instance has properties that are not currently supported by launch configurations, the instances launched by the Amazon EC2 Auto Scaling group might not be identical to the original EC2 instance.