I created an API Gateway (HTTP API) and disabled the default execute-api endpoint. I then created a custom domain in the gateway and an A record in Route53 that points to the API Gateway domain name (which is an execute-api endpoint as well) for the custom domain.
This seems to work fine. However, I noticed if the A record points to the disabled endpoint, there is no change in behavior. I thought that disabling the original endpoint would make it unusable, but it seems Route53 is still able to access it
To add to my confusion, Amazon shows this message when the default endpoint is being disabled:
To allow clients to access your API only by using a custom domain name, disable the default execute-api endpoint. This is an API-level setting that affects all stages of your API. After you enable or disable the default endpoint, a deployment is required for the update to take effect.
So, my question is, how is Route53 able to point an A record to the disabled endpoint?