AWS autoscaling documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for product name consistency
Security assessment
Minor branding update without security context. The change describes network architecture but doesn't introduce or modify security controls.
Diff
diff --git a/autoscaling/plans/userguide/scaling-plan-vpc-endpoints.md b/autoscaling/plans/userguide/scaling-plan-vpc-endpoints.md index f909854fe..4e41155ce 100644 --- a//autoscaling/plans/userguide/scaling-plan-vpc-endpoints.md +++ b//autoscaling/plans/userguide/scaling-plan-vpc-endpoints.md @@ -9 +9 @@ Create an interface VPC endpoint for scaling plansCreate a VPC endpoint policy f -You can use AWS PrivateLink to create a private connection between your VPC and AWS Auto Scaling. You can access AWS Auto Scaling as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Auto Scaling. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Auto Scaling. You can access AWS Auto Scaling as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Auto Scaling.