1 Answer
- Newest
- Most votes
- Most comments
0
I had the same cases a few times and the response from support was to ask support to remove lambda@edge if it is stack and you can't remove it even if it is not associated with any CloudFront distribution.
However, I tried one more solution and it works for me, but I only tried it once.
I attached the lambda@edge to the CloudFront distribution once again for a while and disassociated it once again, then I was able to delete lambda@edge. It looks like it was unblocked somehow after the new association.
answered 2 years ago
Relevant content
- asked a month ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a month ago