AWS autoscaling documentation change
Summary
Updated documentation to consistently use full 'Amazon EC2 Auto Scaling group' terminology instead of 'Auto Scaling group' throughout IAM access control guide
Security assessment
Changes appear to be branding/terminology updates rather than security fixes. No vulnerabilities or security incidents mentioned. Updates improve clarity but don't alter security guidance or address specific vulnerabilities. Security-related examples (like IAM policies) maintain their original intent with updated terminology.
Diff
diff --git a/autoscaling/ec2/userguide/control-access-using-iam.md b/autoscaling/ec2/userguide/control-access-using-iam.md index abce77fc2..718bd9263 100644 --- a//autoscaling/ec2/userguide/control-access-using-iam.md +++ b//autoscaling/ec2/userguide/control-access-using-iam.md @@ -81 +81 @@ The `Resource` JSON policy element specifies the object or objects to which the -You can use ARNs to identify the Auto Scaling groups and launch configurations that the IAM policy applies to. +You can use ARNs to identify the Amazon EC2 Auto Scaling groups and launch configurations that the IAM policy applies to. @@ -83 +83 @@ You can use ARNs to identify the Auto Scaling groups and launch configurations t -An Auto Scaling group has the following ARN. +An Amazon EC2 Auto Scaling group has the following ARN. @@ -93 +93 @@ A launch configuration has the following ARN. -To specify an Auto Scaling group with the `CreateAutoScalingGroup` action, you must replace the UUID with a wildcard (`*`) as shown in the following example. +To specify an Amazon EC2 Auto Scaling group with the `CreateAutoScalingGroup` action, you must replace the UUID with a wildcard (`*`) as shown in the following example. @@ -107 +107 @@ For more information about Amazon EC2 Auto Scaling resource types and their ARNs -For an example of an IAM policy that uses ARNs to control access to Auto Scaling groups, see [Control which Auto Scaling groups can be deleted](./security_iam_id-based-policy-examples.html#policy-example-delete-auto-scaling-group). +For an example of an IAM policy that uses ARNs to control access to Amazon EC2 Auto Scaling groups, see [Control which Amazon EC2 Auto Scaling groups can be deleted](./security_iam_id-based-policy-examples.html#policy-example-delete-auto-scaling-group). @@ -166 +166 @@ The `Condition` element specifies when statements execute based on defined crite -Amazon EC2 Auto Scaling supports the following condition keys that can be used to control access to supported actions and enforce the configuration of Auto Scaling groups: +Amazon EC2 Auto Scaling supports the following condition keys that can be used to control access to supported actions and enforce the configuration of Amazon EC2 Auto Scaling groups: @@ -206 +206 @@ The following condition keys are specific to create launch configuration request -Amazon EC2 Auto Scaling also supports the following global condition keys that you can use to define permissions based on the tags in the request or present on the Auto Scaling group. For more information, see [Tag Auto Scaling groups and instances](./ec2-auto-scaling-tagging.html). +Amazon EC2 Auto Scaling also supports the following global condition keys that you can use to define permissions based on the tags in the request or present on the Amazon EC2 Auto Scaling group. For more information, see [Tag Amazon EC2 Auto Scaling groups and instances](./ec2-auto-scaling-tagging.html). @@ -221 +221 @@ To learn which Amazon EC2 Auto Scaling API actions you can use a condition key w -For examples of IAM policies that use condition keys to control access to supported actions and enforce the configuration of Auto Scaling groups, see the following resources: +For examples of IAM policies that use condition keys to control access to supported actions and enforce the configuration of Amazon EC2 Auto Scaling groups, see the following resources: @@ -223 +223 @@ For examples of IAM policies that use condition keys to control access to suppor - * [Require a launch template and a version number](./ec2-auto-scaling-launch-template-permissions.html#policy-example-launch-template-ex2) – This example enforces that a launch template and the version number of the launch template must be specified when creating or updating Auto Scaling groups. + * [Require a launch template and a version number](./ec2-auto-scaling-launch-template-permissions.html#policy-example-launch-template-ex2) – This example enforces that a launch template and the version number of the launch template must be specified when creating or updating Amazon EC2 Auto Scaling groups. @@ -225 +225 @@ For examples of IAM policies that use condition keys to control access to suppor - * [Control the size of the Auto Scaling groups that can be created](./security_iam_id-based-policy-examples.html#policy-example-min-max-size) – This example enforces constraints on the possible values for the `MinSize` and `MaxSize` properties when creating or updating Auto Scaling groups with a specific tag. + * [Control the size of the Amazon EC2 Auto Scaling groups that can be created](./security_iam_id-based-policy-examples.html#policy-example-min-max-size) – This example enforces constraints on the possible values for the `MinSize` and `MaxSize` properties when creating or updating Amazon EC2 Auto Scaling groups with a specific tag. @@ -227 +227 @@ For examples of IAM policies that use condition keys to control access to suppor - * [Control which scaling policies can be deleted](./security_iam_id-based-policy-examples.html#policy-example-delete-policy) – This example enforces that deleting scaling policies is allowed only for Auto Scaling groups without a specific tag. + * [Control which scaling policies can be deleted](./security_iam_id-based-policy-examples.html#policy-example-delete-policy) – This example enforces that deleting scaling policies is allowed only for Amazon EC2 Auto Scaling groups without a specific tag. @@ -250 +250 @@ For more information about ABAC, see [Define permissions with ABAC authorization -ABAC is possible for resources that support tags, but not everything supports tags. Launch configurations and scaling policies don't support tags, but Auto Scaling groups support tags. +ABAC is possible for resources that support tags, but not everything supports tags. Launch configurations and scaling policies don't support tags, but Amazon EC2 Auto Scaling groups support tags. @@ -252 +252 @@ ABAC is possible for resources that support tags, but not everything supports ta -For more information, see [Tag Auto Scaling groups and instances](./ec2-auto-scaling-tagging.html). +For more information, see [Tag Amazon EC2 Auto Scaling groups and instances](./ec2-auto-scaling-tagging.html). @@ -268 +268 @@ When you create a lifecycle hook that notifies an Amazon SNS topic or Amazon SQS -When you create an Auto Scaling group, you can optionally pass in a service role to allow Amazon EC2 instances to access other AWS services on your behalf. The service role for Amazon EC2 instances (also called the Amazon EC2 instance profile for a launch template or launch configuration) is a special type of service role that is assigned to every EC2 instance in an Auto Scaling group when the instance launches. You can use the IAM console and AWS CLI to create or edit this service role. For more information, see [IAM role for applications that run on Amazon EC2 instances](./us-iam-role.html). +When you create an Amazon EC2 Auto Scaling group, you can optionally pass in a service role to allow Amazon EC2 instances to access other AWS services on your behalf. The service role for Amazon EC2 instances (also called the Amazon EC2 instance profile for a launch template or launch configuration) is a special type of service role that is assigned to every EC2 instance in an Amazon EC2 Auto Scaling group when the instance launches. You can use the IAM console and AWS CLI to create or edit this service role. For more information, see [IAM role for applications that run on Amazon EC2 instances](./us-iam-role.html).