AWS apigateway documentation change
Summary
Updated step 5 to include routing rules as an alternative to base path mappings
Security assessment
This change introduces routing rules as a configuration option but does not explicitly discuss security implications or address vulnerabilities. It appears to be a feature enhancement rather than security-related documentation.
Diff
diff --git a/apigateway/latest/developerguide/apigateway-private-custom-domains-associations.md b/apigateway/latest/developerguide/apigateway-private-custom-domains-associations.md index 525982f25..16f2691f6 100644 --- a//apigateway/latest/developerguide/apigateway-private-custom-domains-associations.md +++ b//apigateway/latest/developerguide/apigateway-private-custom-domains-associations.md @@ -31 +31 @@ If you are an API provider, you must do the following: - 5. Create a base path mapping to map your private API to your private custom domain name. + 5. Create a base path mapping or a routing rule to send traffic from your private API to your private custom domain name. For more information, see [Send traffic to your APIs through your custom domain name in API Gateway](./rest-api-routing-mode.html).