AWS apprunner documentation change
Summary
Updated documentation to state support for dual-stack IP addresses in both incoming/outgoing traffic and added subnet configuration guidance for dual-stack support.
Security assessment
The change includes a note about ensuring subnets support dual-stack traffic, which helps users avoid misconfiguration risks. This is a security-related configuration recommendation but does not resolve a specific vulnerability.
Diff
diff --git a/apprunner/latest/dg/network-pl.md b/apprunner/latest/dg/network-pl.md index 8af9a0020..d38fd4c47 100644 --- a//apprunner/latest/dg/network-pl.md +++ b//apprunner/latest/dg/network-pl.md @@ -23 +23 @@ When your App Runner service is private, you can access your service from within -App Runner currently supports dual-stack (IPv4 and IPv6) address type only for _public_ incoming traffic. For _outgoing traffic_ and _private incoming traffic_ only IPv4 is supported. +App Runner supports IPv4 and dual-stack, (both IPv4 and IPv6), for both incoming traffic and outgoing traffic. @@ -36,0 +37,2 @@ App Runner currently supports dual-stack (IPv4 and IPv6) address type only for _ + * If you're choosing the dual stack option for the IP address type, ensure your subnets can support dual-stack traffic. + @@ -107,4 +108,0 @@ Private endpoint is an App Runner console option that you can choose if you only -###### Note - -Only IPv4 network traffic is supported for Private endpoint. - @@ -123 +121 @@ Incoming traffic -Manage Private endpoint +Manage Private endpoints