AWS apigateway documentation change
Summary
Removed statement about inability to map private APIs to public custom domains, leaving only restriction on public API to private domain mapping
Security assessment
The change removes documentation about a restriction but does not provide evidence of a security vulnerability being addressed. The impact appears to be clarification of domain mapping rules rather than a security fix.
Diff
diff --git a/apigateway/latest/developerguide/apigateway-private-custom-domains.md b/apigateway/latest/developerguide/apigateway-private-custom-domains.md index 12193be6e..6808264b0 100644 --- a//apigateway/latest/developerguide/apigateway-private-custom-domains.md +++ b//apigateway/latest/developerguide/apigateway-private-custom-domains.md @@ -64 +64 @@ The following considerations might impact how you use private custom domain name - * You can't map a public API to a private custom domain name, and you can't map a private API to a public custom domain name. + * You can't map a public API to a private custom domain name.