Certificate is associated with an arn:aws:cloudfront:::xxxxx/xxxx . this cloud front ARN is not showing in Cloudfront list

0

Am trying to delete the certificate from the certificate manager. If I check certificate Associated resources there are some cloudfront ARNs showing as associated resource. But those resources are not available in CloudFront list. How can I delete this certificate / disassociate these resources from certificate ?

The account id showing in Cloudfront ARN is also different from my logged-in accountId. From where these cloud-front resources are creating?

2 Answers
0
Accepted Answer

Hello.
Did you use API Gateway or something similar in your AWS account?
In that case, the following questions are probably similar to yours.
API Gateway may create ALB or CloudFront behind the scenes depending on the configuration.
The effect of this may be that ACM certificates cannot be deleted.
So, if you have been using API Gateway, try deleting the custom domain settings for API Gateway and then deleting the ACM certificate.
https://repost.aws/ja/questions/QU5RI-7lr2R5m_oxe8N6BTRQ/i-can-t-delete-my-certificate-because-it-s-associated-with-an-invisible-cloudfront-distribution

https://repost.aws/knowledge-center/acm-certificate-resources

Deploying an edge-optimized API endpoint creates an Amazon CloudFront distribution by Amazon API Gateway. Deploying a Regional API endpoint creates an Application Load Balancer by API Gateway. The CloudFront distribution or Application Load Balancer is owned by API Gateway, not your account. The ACM certificate provided to deploy API Gateway is associated with the CloudFront distribution or Application Load Balancer.

Try using the following command to remove the certificate.

aws acm delete-certificate --certificate-arn ACM-ARN
profile picture
EXPERT
answered 9 months ago
  • Thanks for your reply,

    Am not using any API gateway.

0

What kind of resource did you use the Certificate for, or when was it created?

You can also have a look on this accepted answer on how to contact the AWS Support in a case similar to yours. You can also let us know if the case was resolved and what was the root cause!

AWS
Piotrek
answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions