1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hello.
It is better to mask the AWS account ID.
Run the following commands to see which resources the certificate is being used for.
Make sure it is not being used for anything other than API Gateway.
https://repost.aws/knowledge-center/acm-certificate-resources
aws acm describe-certificate --certificate-arn ACM-ARN
Regional API endpoint creates an Application Load Balancer by API Gateway.
Presumably, that ALB is the ALB that is created when the region API Gateway is created.
If so, replace or delete the custom domain name associated with the API Gateway.
If you try to remove the ACM certificate after that, it may solve the problem.
Contenus pertinents
- demandé il y a un an
- demandé il y a 3 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
This is not my account number. This is an AWS-owned account number.
The 3 listed associations are the only associations.
Updated answers.
I did this.
The stack deleted the API Gateway custom domain, and the associations were not removed - I believe this is a bug.
For a domain I created today, I was able to create the custom domain manually and then delete it, which removed the associations. For domains I created yesterday, new associations are made and I cannot get rid of the 3 associations that were created yesterday.