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

Enlarge / Be careful with the buckets you put out there for anybody to fill. (credit: Getty Images)

If you're using Amazon Web Services and your S3 storage bucket can be reached from the open web, you'd do well not to pick a generic name for that space. Avoid "example," skip "change_me," don't even go with "foo" or "bar." Someone else with the same "change this later" thinking can cost you a MacBook's worth of cash.

Ask Maciej Pocwierz, who just happened to pick an S3 name...