- 最新
- 投票最多
- 评论最多
Are you sure you have checked all the behaviors of your CloudFront distributions, to make sure the function is not associated anywhere?
If you are confident that is the case, and you've followed all the instructions in the documentation: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-delete-replicas.html then I'd recommend opening a case with AWS support to investigate further.
I only have 2 origins in this account so there aren't a lot of places this could hide, i'm fairly sure i've checked everywhere it could be and it's not there, and it's certainly had more than a few days to figure itself out.
I don't have a support plan tho, so i'm not sure how to contact support about this. I certainly don't want to subscribe to a support plan just to tidy this up. ?Do you know how I raise this without one?
Because the lambda@edge are replicated to edge location, you need to wait for a while. Detache it from CloudFront distribution and wait for a while for AWS to remove replicates.
Normally it should take no more that few minutes. But I also had a situation when I was not able to remove it even after days, then I recommend to contact support and they will remove it for your
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
I have the same error. There are no associated CloudFront distributions for this Lambda for at least several months. It's 100% true, I've checked using https://former2.com/ - there are no associations.
But I'm not able to delete the Lambda@Edge function.