2

I am trying to delete two certificates but I am getting this sort of error message: enter image description here

However when I run:

aws elbv2 describe-load-balancers --region us-east-1 --load-balancer-arns

I get no returned load balancers?

Also if I try to delete directly:

aws elbv2 delete-load-balancer --region us-east-1 --load-balancer-arn ...

I get the error:

is not a valid load balancer ARN

How can I delete these "associations"?

maxisme
  • 3,974
  • 9
  • 47
  • 97

2 Answers2

2

source : https://docs.aws.amazon.com/acm/latest/userguide/troubleshoot-apigateway.html

UPDATE: I had the similar issue recently , as per the attached doc

When you deploy a regional API endpoint, API Gateway creates an application load balancer (ALB) on your behalf. The load balancer is owned by API Gateway and is not visible to you. The ALB is bound to the ACM certificate that you used when deploying your API. To remove the binding and allow ACM to delete your certificate, you must remove the API Gateway custom domain that is associated with the certificate.

As AWS managed ALB was using to the ACM issued certificate and for deleting the cert we need to make sure no resource is using it, but ALB we cant delete as it is AWS managed.

So I had to reach out to AWS support to delete the ALB first and then I was able to delete the cert

AWS support admits that there are already feature requests to resolve this annoying trouble.

samtoddler
  • 8,463
  • 2
  • 26
  • 21
1

As of December 2022, this issue is still possible to run into, and reaching out to Support per @samtoddler's answer is the only way around it.

For those facing this in accounts with no technical support, the AWS team will still be able to help — they have acknowledged this is a recurring issue and involvement of technical teams is required. Don't be discouraged by any messages you may see about "upgrading your support tier" when first describing the issue to them — these are automated, and the non-technical team quickly acknowledged the issue in our most recent case and escalated accordingly.

Might be just coincidental, but after having faced this a couple of times in recent years, in all cases there was some kind of drift involved between a Cloudformation or CDK stack and the AWS Console.

joakim
  • 3,533
  • 2
  • 23
  • 28