AWS autoscaling documentation change
Summary
Updated documentation to consistently use 'Amazon EC2 Auto Scaling group' terminology instead of 'Auto Scaling group' throughout the file
Security assessment
The changes are purely terminological updates to align with official product naming conventions. There is no mention of security vulnerabilities, security patches, or security-related configurations. The example provided focuses on architectural compatibility (ARM vs x86) rather than security controls.
Diff
diff --git a/autoscaling/ec2/userguide/ec2-auto-scaling-mixed-instances-groups-launch-template-overrides.md b/autoscaling/ec2/userguide/ec2-auto-scaling-mixed-instances-groups-launch-template-overrides.md index df3e01dd9..a7f16035c 100644 --- a//autoscaling/ec2/userguide/ec2-auto-scaling-mixed-instances-groups-launch-template-overrides.md +++ b//autoscaling/ec2/userguide/ec2-auto-scaling-mixed-instances-groups-launch-template-overrides.md @@ -5 +5 @@ -Configure an Auto Scaling group to use multiple launch templatesRelated resources +Configure an Amazon EC2 Auto Scaling group to use multiple launch templatesRelated resources @@ -11 +11 @@ In addition to using multiple instance types, you can also use multiple launch t -For example, say that you configure an Auto Scaling group for compute-intensive applications and want to include a mix of C5, C5a, and C6g instance types. However, C6g instances feature an AWS Graviton processor based on 64-bit Arm architecture, while the C5 and C5a instances run on 64-bit Intel x86 processors. The AMIs for C5 and C5a instances both work on each of those instances, but not on C6g instances. To solve this problem, use a different launch template for C6g instances. You can still use the same launch template for C5 and C5a instances. +For example, say that you configure an Amazon EC2 Auto Scaling group for compute-intensive applications and want to include a mix of C5, C5a, and C6g instance types. However, C6g instances feature an AWS Graviton processor based on 64-bit Arm architecture, while the C5 and C5a instances run on 64-bit Intel x86 processors. The AMIs for C5 and C5a instances both work on each of those instances, but not on C6g instances. To solve this problem, use a different launch template for C6g instances. You can still use the same launch template for C5 and C5a instances. @@ -17 +17 @@ This section contains procedures for using the AWS CLI to perform tasks related - * Configure an Auto Scaling group to use multiple launch templates + * Configure an Amazon EC2 Auto Scaling group to use multiple launch templates @@ -24 +24 @@ This section contains procedures for using the AWS CLI to perform tasks related -## Configure an Auto Scaling group to use multiple launch templates +## Configure an Amazon EC2 Auto Scaling group to use multiple launch templates @@ -26 +26 @@ This section contains procedures for using the AWS CLI to perform tasks related -You can configure an Auto Scaling group to use multiple launch templates, as shown in the following examples. +You can configure an Amazon EC2 Auto Scaling group to use multiple launch templates, as shown in the following examples. @@ -28 +28 @@ You can configure an Auto Scaling group to use multiple launch templates, as sho -###### To configure a new Auto Scaling group to use multiple launch templates (AWS CLI) +###### To configure a new Amazon EC2 Auto Scaling group to use multiple launch templates (AWS CLI) @@ -30 +30 @@ You can configure an Auto Scaling group to use multiple launch templates, as sho -Use the [create-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/create-auto-scaling-group.html) command. For example, the following command creates a new Auto Scaling group. It specifies the `c5.large`, `c5a.large`, and `c6g.large` instance types and defines a new launch template for the `c6g.large` instance type to ensure that an appropriate AMI is used to launch Arm instances. Amazon EC2 Auto Scaling uses the order of instance types to determine which instance type to use first when fulfilling On-Demand capacity. +Use the [create-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/create-auto-scaling-group.html) command. For example, the following command creates a new Amazon EC2 Auto Scaling group. It specifies the `c5.large`, `c5a.large`, and `c6g.large` instance types and defines a new launch template for the `c6g.large` instance type to ensure that an appropriate AMI is used to launch Arm instances. Amazon EC2 Auto Scaling uses the order of instance types to determine which instance type to use first when fulfilling On-Demand capacity. @@ -75 +75 @@ The `config.json` file contains the following content. -###### To configure an existing Auto Scaling group to use multiple launch templates (AWS CLI) +###### To configure an existing Amazon EC2 Auto Scaling group to use multiple launch templates (AWS CLI) @@ -77 +77 @@ The `config.json` file contains the following content. -Use the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. For example, the following command assigns the launch template named ``my-launch-template-for-arm`` to the ``c6g.large`` instance type for the Auto Scaling group named ``my-asg``. +Use the [update-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/update-auto-scaling-group.html) command. For example, the following command assigns the launch template named ``my-launch-template-for-arm`` to the ``c6g.large`` instance type for the Amazon EC2 Auto Scaling group named ``my-asg``. @@ -108 +108 @@ The `config.json` file contains the following content. -###### To configure a new Auto Scaling group to use multiple launch templates with attribute-based instance type selection (AWS CLI) +###### To configure a new Amazon EC2 Auto Scaling group to use multiple launch templates with attribute-based instance type selection (AWS CLI) @@ -110 +110 @@ The `config.json` file contains the following content. -Use the [create-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/create-auto-scaling-group.html) command. For example, the following command creates a new Auto Scaling group by specifying a launch template for AWS Graviton instances with an ARM AMI and an additional launch template for AMD or Intel based instances with an x86 AMI. Then, it uses [attribute-based instance selection](./create-mixed-instances-group-attribute-based-instance-type-selection.html) twice to select from a wide range of instance types for each CPU architecture. You can add a similar configuration to an existing Auto Scaling group with the [update-autoscaling-group](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/update-auto-scaling-group.html) command. +Use the [create-auto-scaling-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/autoscaling/create-auto-scaling-group.html) command. For example, the following command creates a new Amazon EC2 Auto Scaling group by specifying a launch template for AWS Graviton instances with an ARM AMI and an additional launch template for AMD or Intel based instances with an x86 AMI. Then, it uses [attribute-based instance selection](./create-mixed-instances-group-attribute-based-instance-type-selection.html) twice to select from a wide range of instance types for each CPU architecture. You can add a similar configuration to an existing Amazon EC2 Auto Scaling group with the [update-autoscaling-group](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/update-auto-scaling-group.html) command. @@ -159 +159 @@ The `config.json` file contains the following content. -###### To verify the launch templates for an Auto Scaling group +###### To verify the launch templates for an Amazon EC2 Auto Scaling group @@ -182 +182 @@ Spot price per unit hour example -Create Auto Scaling groups using launch configurations +Create Amazon EC2 Auto Scaling groups using launch configurations