Hey everyone! I'm currently learning AWS and ran into a frustrating situation with the AWS Certificate Manager (ACM). I created an SSL certificate for `api.railradar.in`, but then noticed some unexpected charges on my account, around **$15**, which took me by surprise since I'm used to free certificates with services like Cloudflare. I didn't see any upfront pricing warnings during the setup process, so I feel a bit blindsided.
When I attempted to delete the certificate, I got a message saying it's "in use" and can't be deleted. It references a resource (`arn:aws:apigateway:ap-south-1::/domainnames/api.railradar.in`), but when I checked the API Gateway console, it showed no custom domains, and my CLI queries confirmed that the domain doesn't actually exist.
I've tried several debugging steps, including checking the domain names and base path mappings in AWS, but I keep getting empty results. The certificate description still shows it as being in use. Since I'm just a student testing out AWS, these unexpected charges are a source of stress for me. I've reached out to AWS Support, but I thought I'd see if anyone else has dealt with similar issues. Any tips on:
- Working around ghost API Gateway domain references?
- Avoiding hidden billing surprises while learning about AWS?
I'd really appreciate any advice or shared experiences!
2 Answers
You aren't alone! It's indeed possible for a backend system to retain ghost resources like that. If this situation results in charges, AWS is often lenient if you explain the issue to them. ACM certificates should be free unless they’re exportable. If you mistakenly set it up that way, just reach out to AWS support—they can check your history and probably waive those charges. Remember, AWS aims to keep customers happy, especially new ones!
It sounds like you might have created an exportable certificate, which isn’t necessary for use with API Gateway. To check associated resources, go to the ACM service in the AWS Management Console and find your certificate. Look at the bottom of the page for any linked resources. As for the unexpected charges, ACM certs are normally free unless they’re exportable. You might want to contact AWS about the billing situation; they can be understanding in these circumstances!
Can you help clarify that? I don’t see that resource on the API Gateway, and I thought I removed it already.
I had a similar experience and learned the hard way about charges. It’s not easy to get all the costs straightened out!
I did try adding a domain for verification but ran into issues. I thought I deleted my API Gateway, but it still shows up on the certificate page.