Re:How an empty S3 bucket can make your AWS bill explode
by jsheard on Monday April 29, 2024 @05:06PM
(#40204140)
Shield Advanced is $3000 per month with a 1 year commitment, plus extra bandwidth fees on top of your existing bandwidth fees, I somehow doubt that many of the users who would be impacted the most by an unexpectedly large bill (individuals and smaller businesses) are proactively paying that much for DDoS insurance just in case.
[ Parent
| on HN ]
Re:How an empty S3 bucket can make your AWS bill explode
by belter on Monday April 29, 2024 @05:50PM
(#40204537)
Agree on that. Was not claiming that Shield Advanced is the solution for this nutty request Rodeo...or maybe we should call it 404 festival...
Re:How an empty S3 bucket can make your AWS bill explode
by tedmiston on Monday April 29, 2024 @10:02PM
(#40206496)
I think CloudWatch billing alarms [1] are the only viable "solution" for an average joe here. Of course, they do not actually stop the usage, but at least they bring automated awareness.
Even with that, there's no easy way to rename an S3 bucket [2], plus doing so would commonly require updating config + re-deploying any apps using the bucket too...
All of this to say, the customer level really feels like the wrong layer of abstraction to solve this problem.
[1]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori...
[2]: https://stackoverflow.com/questions/41511034/how-to-rename-a...