AWS AmazonCloudFront documentation change
Summary
Removed documentation stating IPv6-only subnets are unsupported and that dual-stack Network Load Balancers cannot be added as origins
Security assessment
The changes remove technical restrictions without introducing security content. Removing IPv6-only subnet limitations and dual-stack NLB restrictions indicates feature expansion rather than security fixes. No vulnerabilities, exploits, or security enhancements are mentioned.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/private-content-vpc-origins.md b/AmazonCloudFront/latest/DeveloperGuide/private-content-vpc-origins.md index 41235eb30..a53f0c5fa 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/private-content-vpc-origins.md +++ b//AmazonCloudFront/latest/DeveloperGuide/private-content-vpc-origins.md @@ -40 +40 @@ Your VPC must include the following: - * **Private subnet with at least one available IPv4 address** – CloudFront routes to your subnet by using a service-managed elastic network interface (ENI) that CloudFront creates after you define your VPC origin resource with CloudFront. You must have at least one available IPv4 address in your private subnet so that the ENI creation process can succeed. The IPv4 address can be private, and there is no additional cost for it. IPv6-only subnets are not supported. + * **Private subnet with at least one available IPv4 address** – CloudFront routes to your subnet by using a service-managed elastic network interface (ENI) that CloudFront creates after you define your VPC origin resource with CloudFront. You must have at least one available IPv4 address in your private subnet so that the ENI creation process can succeed. The IPv4 address can be private, and there is no additional cost for it. @@ -53,2 +52,0 @@ In the private subnet, launch an Application Load Balancer, a Network Load Balan - * Dual-stack Network Load Balancers cannot be added as origins -