AWS appstream2 documentation change
Summary
Added notes about IPv6 global addressability, internet access requirements, and the need for ACLs to control traffic.
Security assessment
Documents security implications of IPv6 configuration (e.g., global addressability requiring ACLs) but does not fix a specific vulnerability. Enhances security awareness for network setup.
Diff
diff --git a/appstream2/latest/developerguide/vpc-setup-recommendations.md b/appstream2/latest/developerguide/vpc-setup-recommendations.md index 850931f43..7ed18404f 100644 --- a//appstream2/latest/developerguide/vpc-setup-recommendations.md +++ b//appstream2/latest/developerguide/vpc-setup-recommendations.md @@ -46,0 +47,8 @@ To enhance fault tolerance and reduce the chance of insufficient capacity errors + * If you enable auto assign IPV6 option for your subnet then Elastic Network Interface for your instances will be auto assigned with a global IPV6 address. For more information, see [modify-subnet](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-subnet-attribute.html). + + * Enabling default internet access is only applicable for IPV4 addresses in IPv4 only or dual-stack subnets. To allow internet access for IPV6 addresses add an internet gateway or egress only gateway. For more information, see [egress-only-internet-gateway](https://docs.aws.amazon.com/vpc/latest/userguide/egress-only-internet-gateway.html). + +###### Note + +By default IPV6 addresses are globally addressable. If your subnet has an internet gateway and appropriate subnet groups and acl allowing IPV6 traffic rules your streaming instances can be connected to the internet with IPV6 address. +