- Newest
- Most votes
- Most comments
Hi AWS User,
I guess it is still cached in cloudfront. So what you can do is clearing the cache by creating an invalidation request inside the cloudfront-distribution:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html
If you don't need the cloudfront distribution at all (meaning that if you only had that one single bucket/page listed on this distribution, you could also destroy the distribution.
Sincerely Heiko
hi and thanks for your answer. Yesterday i tried to destroy both the distribution and also the bucket but our site still respond now! i dont't undestand how it is possible! Now i try to invalidate all chache objects (with "/*") in the new distribution that i've created to replace all cloudfront website with landing-page... but nothing changed!
Hi, when I try to reach that site, I get a "Server not found". https://d1hxj3e6rxi2vo.cloudfront.net/
Is it maybe cached locally in your browser?
Sincerley Heiko
Relevant content
- asked a year ago
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 8 months ago
hi and thanks for your answer. Yesterday i tried to destroy both the distribution and also the bucket but our site still respond now! i dont't undestand how it is possible! Now i try to invalidate all chache objects (with "/*") in the new distribution that i've created to replace all cloudfront website with landing-page... but nothing changed!