Custom Domain & API Gateway Connection suddenly disconnected.

Question

I create and deploy API Gateway with lamda by Serverless Framework, and I create and connect Custom domain to API Gateway for each stage like "dev.", "qa.", "release." in Console.
I used them about 3weeks, but it suddenly disconnected when I checked it today morning.

I tried to check lambda by testing, it was fine. Also checked API Gateway by their own domain, it was fine too.
And the domain that I bought from Route53 maybe 3 weeks ago, also has noting of problems. Of course I checked ssl certificate for https still works fine.

What is the problem....

hun_GongLeePrivateFinance · Accepted Answer

The issue was not with Route 53 or API Gateway, but rather because the domain was suspended after failing to verify it within 15 days of purchasing it through Route 53.

re:Post Agent · Answer

Based on the information provided, it seems that the issue lies in the connection between your custom domain and the API Gateway, rather than with the individual components themselves. Here are a few potential reasons and steps to troubleshoot:

1. API Mapping: Check if the API mapping between your custom domain and the API Gateway stage is still intact. Sometimes, these mappings can become disconnected or deleted unintentionally.

2. DNS Configuration: Verify that your DNS settings in Route 53 are still correctly pointing to your API Gateway endpoint. DNS changes can sometimes take time to propagate, so ensure that the records are up-to-date and haven't been altered.

3. Certificate Issues: Although you mentioned the SSL certificate is still working fine, double-check that it hasn't expired or been revoked. Certificates typically have a validity period, and if it's close to expiration, it might cause issues.

4. API Gateway Changes: If there have been any recent deployments or changes to your API Gateway, ensure that these haven't affected the custom domain name configuration.

5. Service-Linked Role: API Gateway uses a service-linked role to manage resources. If this role has been deleted or modified, it could affect the custom domain integration.

6. Regional vs. Edge-Optimized Endpoints: If you've recently changed your API Gateway from a regional to an edge-optimized endpoint (or vice versa), this could affect your custom domain setup.

To resolve the issue:

1. In the API Gateway console, go to the Custom Domain Names section and verify that your domain is still listed and properly configured.

2. Check the API mappings for your custom domain and ensure they are correctly pointing to the right API and stage.

3. If everything looks correct in API Gateway, try removing the custom domain and re-creating it, then re-mapping it to your API.

4. If the problem persists, you may need to contact AWS support for further assistance, as there could be an underlying issue with the API Gateway service itself.

Remember to test thoroughly after making any changes to ensure the connection is re-established correctly.  
**Sources**  
[Custom domain name for public REST APIs in API Gateway - Amazon API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html)  
[Custom domain names for HTTP APIs in API Gateway - Amazon API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-custom-domain-names.html)  
[Custom domain names for WebSocket APIs in API Gateway - Amazon API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/websocket-api-custom-domain-names.html)  
[Using service-linked roles for API Gateway - Amazon API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/using-service-linked-roles.html)

Custom Domain & API Gateway Connection suddenly disconnected.

Relevant content