That's the other side of the coin, the whole idea of AWS and cloudshit is you can scale up and down with little to no maintenance; how many people are playing this game (and how was it monitzed)?
Eh, the
other main idea of cloudshit is to make it as easy to over-engineer and overspend as physically possible to maximize revenue while delivering MVP.
Reminder that until about 5 years ago, there was an "exploit" in AWS S3 where if you could figure out a URL to a valid resource in an S3 bucket, you could spam it with endless unauthenticated traffic and drive the owner's bill into the stratosphere even if the requests were all met with "access denied." It led to increased billing for API calls (
every action in an S3 bucket, from a simple "list files" to "get file metadata" to "retrieve file" has an API cost, and they bill a fixed price per N thousand API calls). The net result is a handful of computers spamming the S3 API endpoint with targeted requests could drive up somebody's AWS bill by thousands or tens of thousands per month.
There was no protection from this, and no "correct" way to configure an S3 bucket to prevent it. Even anonymous unauthenticated calls to the AWS S3 API "counted" against the usage quota, and even buckets set to private with strict IAM policies to prevent anything but "resource X in VPC Y" from doing anything could still be targeted. You just needed to know the name of the bucket and the path/name of an existing resource. Note: per-region, AWS S3 buckets are named in a global namespace per region,
not per user, so if you make a bucket called "bob-bucket-1" in us-east-1a, nobody else on earth can make a bucket with that name in us-east-1a. This, naturally, makes bucket names very easy to guess (since you basically have to invent your own unique naming scheme, and people are boring and typically just use shit like "companyname-things-1").
They finally fixed it (I believe by making failed anonymous API calls "not count" -- your own authenticated API calls still cost you even if they fail for whatever reason, including service unavailability, which still cracks me up) but it took a lot of noise and public embarrassment to get it done.
AWS is dogshit. And the sad thing is it's still the best offering compared to Azure and Google Cloud. Those are poisoned, rancid dogshit.
Using the Concord word is now banned on their official discord, even the jannies are referring to it as "the C word".
Ver archivo adjunto 8652086
kek I wonder if they bothered to censor "cunt" or if "Concord" is the only "c word" they care about. Dumb cunts
