kerfuffle,
@kerfuffle@mastodon.online avatar

People may want to reconsider using #AWS #S3 for static web hosting, or at the bare minimum come up with convoluted names and treat their S3 bucket name as sensitive information. If your S3 bucket name comes up in any web search (for example because it's literally in a public GitHub repo), that's a potential attack vector.

https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1

kerfuffle,
@kerfuffle@mastodon.online avatar
kerfuffle,
@kerfuffle@mastodon.online avatar

And as this was as good an excuse as any, I've gone and migrated all my static sites and deleted all S3 buckets I still had lying around.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • AWS
  • DreamBathrooms
  • ngwrru68w68
  • modclub
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • mdbf
  • GTA5RPClips
  • JUstTest
  • tacticalgear
  • normalnudes
  • tester
  • osvaldo12
  • everett
  • cubers
  • ethstaker
  • anitta
  • provamag3
  • Leos
  • cisconetworking
  • megavids
  • lostlight
  • All magazines