AWS S3 storage bucket with unlucky name nearly cost developer $1,300
Briefly

Avoid generic names for AWS S3 buckets, as seen with Maciej Pocwierz's experience of $1,300 charges due to unauthorized attempts from default open-source tool configurations.
Pocwierz highlights the risk of collecting other people's data with public writes on S3 buckets, emphasizing the importance of taking security warnings seriously.
Read at Ars Technica
[
add
]
[
|
|
]