AWS autoscaling documentation change
Summary
Updated terminology consistency by replacing 'Auto Scaling group' with 'Amazon EC2 Auto Scaling group' throughout document and changed 'Elastic Load Balancing' to 'ELB' abbreviation
Security assessment
Changes are editorial in nature, focusing on service name consistency and abbreviation usage. No modifications to security policies, permissions, or vulnerability disclosures were made. The mention of CloudTrail logging and role deletion procedures maintains existing security documentation without adding new security features.
Diff
diff --git a/autoscaling/ec2/userguide/autoscaling-service-linked-role.md b/autoscaling/ec2/userguide/autoscaling-service-linked-role.md index dc3eb7b6b..ab1c693a2 100644 --- a//autoscaling/ec2/userguide/autoscaling-service-linked-role.md +++ b//autoscaling/ec2/userguide/autoscaling-service-linked-role.md @@ -40 +40 @@ There are two types of Amazon EC2 Auto Scaling service-linked roles: - * The default service-linked role for your account, named AWSServiceRoleForAutoScaling. This role is automatically assigned to your Auto Scaling groups unless you specify a different service-linked role. + * The default service-linked role for your account, named AWSServiceRoleForAutoScaling. This role is automatically assigned to your Amazon EC2 Auto Scaling groups unless you specify a different service-linked role. @@ -47 +47 @@ There are two types of Amazon EC2 Auto Scaling service-linked roles: -The permissions of a custom suffix service-linked role are identical to those of the default service-linked role. In both cases, you cannot edit the roles, and you also cannot delete them if they are still in use by an Auto Scaling group. The only difference is the role name suffix. +The permissions of a custom suffix service-linked role are identical to those of the default service-linked role. In both cases, you cannot edit the roles, and you also cannot delete them if they are still in use by an Amazon EC2 Auto Scaling group. The only difference is the role name suffix. @@ -53 +53 @@ You can specify either role when you edit your AWS Key Management Service key po - * The ability to track which Auto Scaling group made an API call in your CloudTrail logs + * The ability to track which Amazon EC2 Auto Scaling group made an API call in your CloudTrail logs @@ -88 +88 @@ The role permissions policy, [AutoScalingServiceRolePolicy](https://docs.aws.ama - * `elasticloadbalancing` – Register and deregister instances with Elastic Load Balancing and check the health of registered targets. + * `elasticloadbalancing` – Register and deregister instances with ELB and check the health of registered targets. @@ -113 +113 @@ Amazon EC2 Auto Scaling supports using service-linked roles in all of the AWS Re -Amazon EC2 Auto Scaling creates the AWSServiceRoleForAutoScaling service-linked role for you the first time that you create an Auto Scaling group, unless you manually create a custom suffix service-linked role and specify it when creating the group. +Amazon EC2 Auto Scaling creates the AWSServiceRoleForAutoScaling service-linked role for you the first time that you create an Amazon EC2 Auto Scaling group, unless you manually create a custom suffix service-linked role and specify it when creating the group. @@ -184 +184 @@ You cannot edit the service-linked roles that are created for Amazon EC2 Auto Sc -If you are not using an Auto Scaling group, we recommend that you delete its service-linked role. Deleting the role prevents you from having an entity that is not used or actively monitored and maintained. +If you are not using an Amazon EC2 Auto Scaling group, we recommend that you delete its service-linked role. Deleting the role prevents you from having an entity that is not used or actively monitored and maintained. @@ -186 +186 @@ If you are not using an Auto Scaling group, we recommend that you delete its ser -You can delete a service-linked role only after first deleting the related dependent resources. This protects you from inadvertently revoking Amazon EC2 Auto Scaling permissions to your resources. If a service-linked role is used with multiple Auto Scaling groups, you must delete all Auto Scaling groups that use the service-linked role before you can delete it. For more information, see [Delete your Auto Scaling infrastructure](./as-process-shutdown.html). +You can delete a service-linked role only after first deleting the related dependent resources. This protects you from inadvertently revoking Amazon EC2 Auto Scaling permissions to your resources. If a service-linked role is used with multiple Amazon EC2 Auto Scaling groups, you must delete all Amazon EC2 Auto Scaling groups that use the service-linked role before you can delete it. For more information, see [Delete your Amazon EC2 Auto Scaling infrastructure](./as-process-shutdown.html). @@ -190 +190 @@ You can use IAM to delete a service-linked role. For more information, see [Dele -If you delete the AWSServiceRoleForAutoScaling service-linked role, Amazon EC2 Auto Scaling creates the role again when you create an Auto Scaling group and do not specify a different service-linked role. +If you delete the AWSServiceRoleForAutoScaling service-linked role, Amazon EC2 Auto Scaling creates the role again when you create an Amazon EC2 Auto Scaling group and do not specify a different service-linked role.