I briefly looked at AWS S3 Glacier storage, thinking maybe having a second cloud host for my backups would be good.
I can't actually figure out how much this will cost me because they charge per operation (you know, like PUT, GET, etc.) in addition to the storage costs (which I easily figured out).
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.
The whole S3 charging for unauthorized/denied accesses to #S3 shows exactly the culture of #Amazon . Just because they reversed this policy (TBD if they actually do) doesn't mean that other similar policies will be changed. That the support person couldn't raise concerns, that the middle managers didn't care enough about the customers to realize how bad/stupid/damaging it is.
I haven’t tested this myself, but it seems this may be a very nasty way to inflict targeted or random harm against anyone with #AWS#S3 buckets. #infosec
Wahnsinn. Die #Amazon#Cloud ist ja wirklich ein tolles Ding ... um Amazon Geld zu besorgen. 🤣
Wirklich unglaublich, was man da liest. Da werden viele Firmen teures Lehrgeld zahlen, bis sie wegen Kostenexplosion vielleicht doch wieder in eigenes Wissen und Know-How investieren, sofern noch möglich ...