AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' throughout the document for consistency and clarity.
Security assessment
The changes are purely terminological updates without introducing new security concepts, addressing vulnerabilities, or modifying security configurations. No evidence of security incidents or weaknesses being resolved.
Diff
diff --git a/autoscaling/ec2/userguide/getting-started-vpc-lattice.md b/autoscaling/ec2/userguide/getting-started-vpc-lattice.md index 7950de2d1..3835077a6 100644 --- a//autoscaling/ec2/userguide/getting-started-vpc-lattice.md +++ b//autoscaling/ec2/userguide/getting-started-vpc-lattice.md @@ -7 +7 @@ Security groups: Inbound and outbound rulesLimitations -# Prepare to attach a VPC Lattice target group to your Auto Scaling group +# Prepare to attach a VPC Lattice target group to your Amazon EC2 Auto Scaling group @@ -9 +9 @@ Security groups: Inbound and outbound rulesLimitations -Before you attach a VPC Lattice target group to your Auto Scaling group, you must complete the following prerequisites: +Before you attach a VPC Lattice target group to your Amazon EC2 Auto Scaling group, you must complete the following prerequisites: @@ -21 +21 @@ Before you attach a VPC Lattice target group to your Auto Scaling group, you mus - * The target group must be in the same AWS account, VPC, and Region as your Auto Scaling group. + * The target group must be in the same AWS account, VPC, and Region as your Amazon EC2 Auto Scaling group. @@ -23 +23 @@ Before you attach a VPC Lattice target group to your Auto Scaling group, you mus - * The target group must specify a target type of `instance`. You can't specify a target type of `ip` when using an Auto Scaling group. + * The target group must specify a target type of `instance`. You can't specify a target type of `ip` when using an Amazon EC2 Auto Scaling group. @@ -25 +25 @@ Before you attach a VPC Lattice target group to your Auto Scaling group, you mus - * You must have sufficient IAM permissions to attach the target group to the Auto Scaling group. The following example policy shows the minimum required permissions that are necessary to attach and detach target groups. + * You must have sufficient IAM permissions to attach the target group to the Amazon EC2 Auto Scaling group. The following example policy shows the minimum required permissions that are necessary to attach and detach target groups. @@ -51 +51 @@ JSON - * If the launch template for your Auto Scaling group does not contain the correct settings for VPC Lattice, such as a compatible security group, you must update the launch template. Existing instances are not updated with the new settings when the launch template is modified. To update existing instances, you can start an instance refresh to replace the instances. For more information, see [Use an instance refresh to update instances in an Auto Scaling group](./asg-instance-refresh.html). + * If the launch template for your Amazon EC2 Auto Scaling group does not contain the correct settings for VPC Lattice, such as a compatible security group, you must update the launch template. Existing instances are not updated with the new settings when the launch template is modified. To update existing instances, you can start an instance refresh to replace the instances. For more information, see [Use an instance refresh to update instances in an Amazon EC2 Auto Scaling group](./asg-instance-refresh.html). @@ -53 +53 @@ JSON - * Before enabling the VPC Lattice health checks on your Auto Scaling group, you can configure an application-based health check to verify that your application is responding as expected. For more information, see [Health checks for your target groups](https://docs.aws.amazon.com/vpc-lattice/latest/ug/target-group-health-checks.html) in the _VPC Lattice User Guide_. + * Before enabling the VPC Lattice health checks on your Amazon EC2 Auto Scaling group, you can configure an application-based health check to verify that your application is responding as expected. For more information, see [Health checks for your target groups](https://docs.aws.amazon.com/vpc-lattice/latest/ug/target-group-health-checks.html) in the _VPC Lattice User Guide_. @@ -66 +66 @@ Network configuration is sufficiently complex that we strongly recommend that yo -To learn more about creating security groups for VPC Lattice that you can use with your Auto Scaling group, see [Control traffic using security groups](https://docs.aws.amazon.com/vpc-lattice/latest/ug/security-groups.html) in the _VPC Lattice User Guide_. To troubleshoot issues with traffic flow, consult the _VPC Lattice User Guide_ for further information. +To learn more about creating security groups for VPC Lattice that you can use with your Amazon EC2 Auto Scaling group, see [Control traffic using security groups](https://docs.aws.amazon.com/vpc-lattice/latest/ug/security-groups.html) in the _VPC Lattice User Guide_. To troubleshoot issues with traffic flow, consult the _VPC Lattice User Guide_ for further information. @@ -74 +74 @@ Description | A description to help you identify the security group. -VPC | The same VPC as the Auto Scaling group. +VPC | The same VPC as the Amazon EC2 Auto Scaling group. @@ -80 +80 @@ When you create a security group, it has no inbound rules. No inbound traffic or -To allow clients within a VPC Lattice service network to connect to instances in your Auto Scaling group, the security group for your Auto Scaling group must be set up correctly. In this case, give it an inbound rule to allow traffic from the name of the AWS managed prefix list for VPC Lattice, instead of a specific IP address. The VPC Lattice prefix list is a range of IP addresses used by VPC Lattice in CIDR notation. For more information, see [Work with AWS-managed prefix lists](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-aws-managed-prefix-lists.html) in the _Amazon VPC User Guide_. +To allow clients within a VPC Lattice service network to connect to instances in your Amazon EC2 Auto Scaling group, the security group for your Amazon EC2 Auto Scaling group must be set up correctly. In this case, give it an inbound rule to allow traffic from the name of the AWS managed prefix list for VPC Lattice, instead of a specific IP address. The VPC Lattice prefix list is a range of IP addresses used by VPC Lattice in CIDR notation. For more information, see [Work with AWS-managed prefix lists](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-aws-managed-prefix-lists.html) in the _Amazon VPC User Guide_. @@ -89 +89 @@ HTTPS rule | Type: HTTPS Source: com.amazonaws.`region`.vpc-lattice -The security group is stateful: it allows traffic from clients within the VPC Lattice service network to instances in your Auto Scaling group, and then sends the response back to the client it previously left. +The security group is stateful: it allows traffic from clients within the VPC Lattice service network to instances in your Amazon EC2 Auto Scaling group, and then sends the response back to the client it previously left. @@ -97 +97 @@ By default, a security group includes an outbound rule that allows all outbound - * [Mixed instances groups](./ec2-auto-scaling-mixed-instances-groups.html) are supported. If you attach a VPC Lattice target group to an Auto Scaling group that has a mixed instances policy, the load balancing algorithm evenly distributes load onto all available resources and assumes that instances are similar enough to handle equal loads. + * [Mixed instances groups](./ec2-auto-scaling-mixed-instances-groups.html) are supported. If you attach a VPC Lattice target group to an Amazon EC2 Auto Scaling group that has a mixed instances policy, the load balancing algorithm evenly distributes load onto all available resources and assumes that instances are similar enough to handle equal loads.