AWS apigateway documentation change
Summary
Updated documentation about wildcard custom domain name usage, including routing behavior clarification and subdomain management guidance
Security assessment
The changes clarify routing behavior and subdomain management but do not address specific security vulnerabilities. The removal of redundant configuration statements and addition of routing examples are operational improvements rather than security fixes. No evidence of CVE mitigation or security incident response.
Diff
diff --git a/apigateway/latest/developerguide/how-to-custom-domains.md b/apigateway/latest/developerguide/how-to-custom-domains.md index 7c15b8294..b8c4eaf96 100644 --- a//apigateway/latest/developerguide/how-to-custom-domains.md +++ b//apigateway/latest/developerguide/how-to-custom-domains.md @@ -74 +74 @@ If your application uses certificate pinning, sometimes known as SSL pinning, to -With wildcard custom domain names, you can support an almost infinite number of domain names without exceeding the [default quota](./limits.html). For example, you could give each of your customers their own domain name, ``customername`.api.example.com`. +With wildcard custom domain names, you can support an almost infinite number of domain names without exceeding the [default quota](./limits.html). For example, you could give each of your customers their own domain name, ``customername`.example.com`. @@ -78 +78,7 @@ To create a wildcard custom domain name, specify a wildcard (`*`) as the first s -For example, the wildcard custom domain name `*.example.com` results in subdomains such as `a.example.com`, `b.example.com`, and `c.example.com`, which all route to the same domain. +For example, the wildcard custom domain name `*.example.com` results in subdomains such as `a.example.com`, `b.example.com`, and `c.example.com`. When you create the wildcard custom domain name, all its subdomains are routed by the routing mode of the wildcard domain name. To route subdomains to different APIs, you can do either of the following: + + * Use routing rules to route incoming requests to `*.example.com` to different target REST APIs using the `Host` header. For more information, see [Example 4: Routing rules for wildcard domain names](./rest-api-routing-rules-examples.html#rest-api-routing-rules-examples-rule-for-wildcard-domains). + + * Create a domain name for any subdomains that you want to route to a different endpoint. In a single AWS account, you can have both `*.example.com` and `a.example.com`. + + @@ -80 +85,0 @@ For example, the wildcard custom domain name `*.example.com` results in subdomai -Wildcard custom domain names support distinct configurations from API Gateway's standard custom domain names. For example, in a single AWS account, you can configure `*.example.com` and `a.example.com` to behave differently. @@ -106 +111 @@ The following are next steps for custom domain names. - * To learn how to connect API stages to a custom domain name, see [Map API stages to a custom domain name for REST APIs](./rest-api-mappings.html). + * To learn how to connect API stages to a custom domain name, see [Send traffic to your APIs through your custom domain name in API Gateway](./rest-api-routing-mode.html).