AWS apigateway: Fix typo in REST API disable default endpoint doc
Summary
Corrects a typo in the text describing when disabling the default execute-api endpoint takes effect ('takes affect' -> 'takes effect'). No substantive technical or security content changed.
Security assessment
The only change is a spelling correction ('takes affect' to 'takes effect'); the surrounding security guidance on disabling the default execute-api endpoint and the 403 Forbidden behavior is unchanged, so there is no security-relevant edit.
Evidence
+By default, clients can invoke your API by using the `execute-api` endpoint that API Gateway generates for your API. To ensure that clients can access your API only by using a custom domain name, disable the default `execute-api` endpoint. Clients can still connect to your default endpoint, but they will receive a `403 Forbidden` status code. Disabling the default endpoint affects all stages of the API. This setting takes effect when you update any setting on any stage, such as updating the deployment on the stage.
Diff
diff --git a/apigateway/latest/developerguide/rest-api-disable-default-endpoint.md b/apigateway/latest/developerguide/rest-api-disable-default-endpoint.md index dffeb9622..a08a44a62 100644 --- a//apigateway/latest/developerguide/rest-api-disable-default-endpoint.md +++ b//apigateway/latest/developerguide/rest-api-disable-default-endpoint.md @@ -9 +9 @@ -By default, clients can invoke your API by using the `execute-api` endpoint that API Gateway generates for your API. To ensure that clients can access your API only by using a custom domain name, disable the default `execute-api` endpoint. Clients can still connect to your default endpoint, but they will receive a `403 Forbidden` status code. Disabling the default endpoint affects all stages of the API. This setting takes affect when you update any setting on any stage, such as updating the deployment on the stage. +By default, clients can invoke your API by using the `execute-api` endpoint that API Gateway generates for your API. To ensure that clients can access your API only by using a custom domain name, disable the default `execute-api` endpoint. Clients can still connect to your default endpoint, but they will receive a `403 Forbidden` status code. Disabling the default endpoint affects all stages of the API. This setting takes effect when you update any setting on any stage, such as updating the deployment on the stage.