- Mais recentes
- Mais votos
- Mais comentários
For the inability to delete the ACM record used with API Gateway, see this article: https://repost.aws/questions/QU63csgGNEQl2M--xCdy-oxw/cant-delete-certificate-because-there-are-dangling-load-balancer-resources
For the attempt to reuse the domain, most likely, it is not a load balancer that is causing this. When you setup an ELB, you use a CNAME or alias record to point the traffic to the ELB: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html#routing-to-elb-load-balancer-configuring
The DNS record would be the problem, not the ELB itself. Check the DNS server setup for the domain in question or query any DNS server via a tool like dig or nslookup.
dig your_domain
Any response that resolves to an IP means the hostname is in use for something else. If it is CNAME'd or aliased to an ELB as you suspect, you would need to delete the CNAME/alias DNS record.
If you remove a CNAME/alias but still get the error, another CloudFront distribution could be using the domain. To fix that, Disable the CloudFront distribution currently using the domain name. Follow this doc to Disable it: https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cnamealreadyexists-error/
If still not fixed, check if API Gateway has the domain setup as a custom domain. If yes, delete the custom domain. Look at this document on creating regional domains, delete the existing alias for your domain instead of creating a new one. https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-regional-api-custom-domain-create.html
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há um ano
Please raise a support case with ACM team on this. They will help you resolve this issue.