AWS apigateway documentation change
Summary
Changed 'allow IPv4 addresses' to 'resolve IPv4 addresses' in API invocation context
Security assessment
Terminology update focuses on DNS resolution mechanics, not security policy changes. Existing security recommendations about dualstack remain unaffected.
Diff
diff --git a/apigateway/latest/developerguide/http-api-ip-address-type.md b/apigateway/latest/developerguide/http-api-ip-address-type.md index 54a1c7727..36d0ccc7b 100644 --- a//apigateway/latest/developerguide/http-api-ip-address-type.md +++ b//apigateway/latest/developerguide/http-api-ip-address-type.md @@ -9 +9 @@ Considerations for IP address typesChange the IP address type of an HTTP API -When you create an API, you specify the type of IP addresses that can invoke your API. You can choose IPv4 to allow IPv4 addresses to invoke your API, or you can choose dualstack to allow both IPv4 and IPv6 addresses to invoke your API. You might want to set the IP address type to dualstack to alleviate IP space exhaustion or for your security posture. For more information about the benefits of a dualstack IP address type, see [IPv6 on AWS](https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html). +When you create an API, you specify the type of IP addresses that can invoke your API. You can choose IPv4 to resolve IPv4 addresses to invoke your API, or you can choose dualstack to allow both IPv4 and IPv6 addresses to invoke your API. You might want to set the IP address type to dualstack to alleviate IP space exhaustion or for your security posture. For more information about the benefits of a dualstack IP address type, see [IPv6 on AWS](https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html).