Fail on delete of the stack about cloudfront-authorization-at-edge

[ottokruse]

So the original error reason for the failed delete of the us-east-1 stack was that the bucket was non-empty?

That's annoying and we should fix that!

Not sure why you shouldn't be able to remove the stacks after cleaning the buckets yourself. You should be able to try the delete again. Maybe use AWS CLI (not SAM): aws cloudformation delete-stack --stack-name sam-stack-name

[reisub83]

The second error, after cleaning the bucket, was related to the Lambda@Edge function association in Cloudfront Behaviors.
We had to manually remove associations , wait some time (for cloudfront to propagate to edge nodes, I think), and than the sam delete in us-east-1 has worked

[ottokruse]

Ok. That is also an annoying one, and I know of no other work around than to wait as you do.

I did implement S3 empty bucket in #243 (and released v2.1.7). One less annoying thing to worry about ;)

Will close this issue as the other issue is beyond the control of this solution. It must be fixed/improved by the AWS service team.