- Newest
- Most votes
- Most comments
Constructive feedback: I have the same issue, and besides, my domain is blocked, the distribution is busted, it does not work and keeps my domain locked. I cannot wait for end of the billing cycle. Do you guys understand that customers and managers do not buy that kind of excuse?
answered 10 months ago
I also have the same issue. It will be better if you change the code to delete the distribution.
answered 10 months ago
Agreed this is nonsense behavior for "Free" tier. There needs to be a way to easily cleanup/remove testing work.
answered 8 months ago
You're encountering a limitation with CloudFront distributions that are subscribed to pricing plans, including the Free tier plan. According to AWS documentation, you cannot delete a distribution that is subscribed to any pricing plan until you first cancel the plan and wait for the current billing cycle to end.
The behavior you're experiencing is actually documented functionality, not a bug. When you changed from the 'Free' plan to pay-as-you-go, this change won't take effect until the start of the next calendar month (the end of the current billing cycle). Until that time, the distribution is still considered to be on the 'Free' pricing plan.
The restriction applies to all pricing plans, including the Free tier. The system treats all pricing plans the same way in terms of deletion restrictions, regardless of whether it's a paid plan or the Free plan.
Your only option is to wait until the current billing cycle ends (the end of the calendar month), at which point your distribution will be on the pay-as-you-go model and can then be deleted. While this may be inconvenient for testing purposes, it's the current designed behavior of the service.
Sources
CloudFront flat-rate pricing plans - Amazon CloudFront
Delete a distribution - Amazon CloudFront
Please elaborate on how this is 'functionality'. What function is this behaviour providing?
It is later stated that this is 'the current designed behavior'. I find it very hard to believe that anyone would intentionally design it this way. It seems much more like an oversight or side-effect that has not yet been deemed high priority enough to be corrected or improved.
Relevant content
asked 4 years ago
asked 9 months ago
asked 2 years ago
- AWS OFFICIALUpdated a year ago
I have the same problem. Were you able to solve it?
Thanks!
As I mentioned, I had to [bizarrely] change the distribution from 'Free' to pay-as-you-go and then wait until that actually took effect at the end of the calendar month. When the next calendar month had begun, the distribution was then a pay-as-you-go one and I was able to delete it (as I had already disabled it).
The problem wasn't not being able to delete it, the problem was not being able to do so right away, and having to change the distribution payment plan to be able to do so, and having to wait days/weeks for that to take effect before being able to go further. So, effectively, a problem of an unavoidable delay before being able to delete the distribution.
Thank you for clarifying, and I completely agree. Needing to change plans and wait just to delete a distribution is unnecessary and should definitely be fixed.