1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren