AWS autoscaling documentation change
Summary
Updated documentation to indicate mixed instances groups are now supported with VPC Lattice target groups, removing previous error message and compatibility restriction
Security assessment
The change reflects feature capability expansion rather than addressing a security vulnerability. No security implications or mitigations are mentioned in the diff.
Diff
diff --git a/autoscaling/ec2/userguide/getting-started-vpc-lattice.md b/autoscaling/ec2/userguide/getting-started-vpc-lattice.md index a006f20fd..110c76ebe 100644 --- a//autoscaling/ec2/userguide/getting-started-vpc-lattice.md +++ b//autoscaling/ec2/userguide/getting-started-vpc-lattice.md @@ -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 not supported. If you try to attach a VPC Lattice target group to an Auto Scaling group that has a mixed instances policy, you receive the error message **Currently, Auto Scaling Groups with mixed instances cannot be integrated with a VPC Lattice service**. This is because 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 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.