AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for branding consistency. Minor phrasing adjustments in placement group and Spot Instance sections.
Security assessment
Changes are purely terminological updates (branding consistency) and minor clarifications. No security vulnerabilities, patches, or new security features are mentioned. Existing security-related content (like IAM roles and termination protection) remains unchanged.
Diff
diff --git a/autoscaling/ec2/userguide/advanced-settings-for-your-launch-template.md b/autoscaling/ec2/userguide/advanced-settings-for-your-launch-template.md index 0b7916636..94c3c34be 100644 --- a//autoscaling/ec2/userguide/advanced-settings-for-your-launch-template.md +++ b//autoscaling/ec2/userguide/advanced-settings-for-your-launch-template.md @@ -45 +45 @@ Choose the Amazon Machine Image (AMI) that you want to use. You can either searc -Choose an instance type that is compatible with your AMI. You can skip adding an instance type to your launch template if you plan to use multiple instances types that are embedded in the Auto Scaling group's own resource definition. An instance type is only required if you don't plan to create a [mixed instances group](./ec2-auto-scaling-mixed-instances-groups.html). +Choose an instance type that is compatible with your AMI. You can skip adding an instance type to your launch template if you plan to use multiple instances types that are embedded in the Amazon EC2 Auto Scaling group's own resource definition. An instance type is only required if you don't plan to create a [mixed instances group](./ec2-auto-scaling-mixed-instances-groups.html). @@ -51 +51 @@ The advanced settings are optional. If you do not configure any advanced setting -Expand the **Advanced details** section to view the advanced settings. The following sections describe the most useful advanced settings to focus on when creating a launch template for an Auto Scaling group. For more information, see [Advanced details](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-launch-template.html#lt-advanced-details) in the _Amazon EC2 User Guide_. +Expand the **Advanced details** section to view the advanced settings. The following sections describe the most useful advanced settings to focus on when creating a launch template for an Amazon EC2 Auto Scaling group. For more information, see [Advanced details](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-launch-template.html#lt-advanced-details) in the _Amazon EC2 User Guide_. @@ -56 +56 @@ Expand the **Advanced details** section to view the advanced settings. The follo -The instance profile contains the IAM role that you want to use. When your Auto Scaling group launches an EC2 instance, the permissions defined in the associated IAM role are granted to applications running on the instance. For more information, see [IAM role for applications that run on Amazon EC2 instances](./us-iam-role.html). +The instance profile contains the IAM role that you want to use. When your Amazon EC2 Auto Scaling group launches an EC2 instance, the permissions defined in the associated IAM role are granted to applications running on the instance. For more information, see [IAM role for applications that run on Amazon EC2 instances](./us-iam-role.html). @@ -66 +66 @@ When enabled, this feature prevents users from terminating an instance using the -You can enable detailed monitoring for your EC2 instances to allow them to send metric data to Amazon CloudWatch at 1-minute intervals. By default, EC2 instances send metric data to CloudWatch at 5-minute intervals. Additional charges apply. For more information, see [Configure monitoring for Auto Scaling instances](./enable-as-instance-metrics.html). +You can enable detailed monitoring for your EC2 instances to allow them to send metric data to Amazon CloudWatch at 1-minute intervals. By default, EC2 instances send metric data to CloudWatch at 5-minute intervals. Additional charges apply. For more information, see [Configure monitoring for Amazon EC2 Auto Scaling instances](./enable-as-instance-metrics.html). @@ -71 +71 @@ You can enable detailed monitoring for your EC2 instances to allow them to send -Amazon EC2 provides burstable performance instances, such as T2, T3, and T3a, that allow applications to burst beyond the baseline CPU performance when required. By default, these instances can burst for a limited time before their CPU usage is throttled. You can optionally enable unlimited mode so that the instances can burst beyond the baseline for as long as needed. This allows applications to sustain high CPU performance when required. Additional charges may apply. For more information, see [Use an Auto Scaling group to launch a burstable performance instance as Unlimited](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-how-to.html#burstable-performance-instances-auto-scaling-grp) in the _Amazon EC2 User Guide_. +Amazon EC2 provides burstable performance instances, such as T2, T3, and T3a, that allow applications to burst beyond the baseline CPU performance when required. By default, these instances can burst for a limited time before their CPU usage is throttled. You can optionally enable unlimited mode so that the instances can burst beyond the baseline for as long as needed. This allows applications to sustain high CPU performance when required. Additional charges may apply. For more information, see [Use an Amazon EC2 Auto Scaling group to launch a burstable performance instance as Unlimited](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-how-to.html#burstable-performance-instances-auto-scaling-grp) in the _Amazon EC2 User Guide_. @@ -76 +76 @@ Amazon EC2 provides burstable performance instances, such as T2, T3, and T3a, th -You can specify a placement group and use a cluster or a partition strategy to influence how your instances are physically located in the AWS data center. For small Auto Scaling groups, you can also use the spread strategy. For more information, see [Placement groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html) in the _Amazon EC2 User Guide_. +You can specify a placement group and use a cluster or a partition strategy to influence how your instances are physically located in the AWS data center. For small Amazon EC2 Auto Scaling groups, you can also use the spread strategy. For more information, see [Placement groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html) in the _Amazon EC2 User Guide_. @@ -78 +78 @@ You can specify a placement group and use a cluster or a partition strategy to i -There are some considerations when using placement groups with Auto Scaling groups: +There are some considerations when using placement groups with Amazon EC2 Auto Scaling groups: @@ -80 +80 @@ There are some considerations when using placement groups with Auto Scaling grou - * If a placement group is specified in both the launch template and the Auto Scaling group, the placement group for the Auto Scaling group takes precedence. + * If a placement group is specified in both the launch template and the Amazon EC2 Auto Scaling group, the placement group for the Amazon EC2 Auto Scaling group takes precedence. @@ -82 +82 @@ There are some considerations when using placement groups with Auto Scaling grou - * In CloudFormation, be careful if you define a placement group in the launch template. Amazon EC2 Auto Scaling will launch instances into the specified placement group. However, CloudFormation will not receive signals from those instances if you use an [UpdatePolicy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) with your Auto Scaling group (though this could change in the future). + * In CloudFormation, be careful if you define a placement group in the launch template. Amazon EC2 Auto Scaling will launch instances into the specified placement group. However, CloudFormation will not receive signals from those instances if you use an [UpdatePolicy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html) with your Amazon EC2 Auto Scaling group (though this could change in the future). @@ -90 +90 @@ There are some considerations when using placement groups with Auto Scaling grou -You can choose **Request Spot Instances** to request Spot Instances at the Spot price, capped at the On-Demand price, and choose **Customize** to change the default Spot Instance settings. For an Auto Scaling group, you must specify a one-time request with no end date (the default). For more information, see [Request Spot Instances for fault-tolerant and flexible applications](./launch-template-spot-instances.html). This setting may be useful in special circumstances, but in general it's best to leave it unspecified and create a mixed instances group instead. For more information, see [Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). +You can choose **Request Spot Instances** to request Spot Instances at the Spot price, capped at the On-Demand price, and choose **Customize** to change the default Spot Instance settings. For an Amazon EC2 Auto Scaling group, you must specify a one-time request with no end date (the default). For more information, see [Request Spot Instances for fault-tolerant and flexible applications](./launch-template-spot-instances.html). This setting may be useful in special circumstances, but in general it's best to leave it unspecified and create a mixed instances group instead. For more information, see [Amazon EC2 Auto Scaling groups with multiple instance types and purchase options](./ec2-auto-scaling-mixed-instances-groups.html). @@ -92 +92 @@ You can choose **Request Spot Instances** to request Spot Instances at the Spot -If you specify a Spot Instance request in your launch template, you can't create a mixed instances group. If you try to use a launch template that requests Spot Instances with a mixed instances group, you receive the following error message: `Incompatible launch template: You cannot use a launch template that is set to request Spot Instances (InstanceMarketOptions) when you configure an Auto Scaling group with a mixed instances policy. Add a different launch template to the group and try again.` +If you specify a Spot Instance request in your launch template, you can't create a mixed instances group. If you try to use a launch template that requests Spot Instances with a mixed instances group, you receive the following error message: `Incompatible launch template: You cannot use a launch template that is set to request Spot Instances (InstanceMarketOptions) when you configure an Amazon EC2 Auto Scaling group with a mixed instances policy. Add a different launch template to the group and try again.` @@ -110 +110 @@ You can choose whether to launch instances into: -To target a specific Capacity Reservation, the instance type in your launch template must match the instance type of the reservation. When you create your Auto Scaling group, use the same Availability Zone as the Capacity Reservation. Depending on the AWS Region you choose, you can choose to target a Capacity Block instead. For more information, see [Use Capacity Blocks for machine learning workloads](./launch-template-capacity-blocks.html). +To target a specific Capacity Reservation, the instance type in your launch template must match the instance type of the reservation. When you create your Amazon EC2 Auto Scaling group, use the same Availability Zone as the Capacity Reservation. Depending on the AWS Region you choose, you can choose to target a Capacity Block instead. For more information, see [Use Capacity Blocks for machine learning workloads](./launch-template-capacity-blocks.html). @@ -167 +167 @@ You can customize and finish configuring your instances at launch time by specif -If you have large downloads or complex scripts, this adds to the time it takes for the instance to become ready for use. In which case, you may need to configure a lifecycle hook to delay an instance from reaching the `InService` state until it's fully provisioned. For more information about adding a lifecycle hook to your Auto Scaling group, see [Amazon EC2 Auto Scaling lifecycle hooks](./lifecycle-hooks.html). +If you have large downloads or complex scripts, this adds to the time it takes for the instance to become ready for use. In which case, you may need to configure a lifecycle hook to delay an instance from reaching the `InService` state until it's fully provisioned. For more information about adding a lifecycle hook to your Amazon EC2 Auto Scaling group, see [Amazon EC2 Auto Scaling lifecycle hooks](./lifecycle-hooks.html). @@ -175 +175 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Create a launch template for an Auto Scaling group +Create a launch template for an Amazon EC2 Auto Scaling group