AWS Purity Test
awspuritytest.com
awspuritytest.com
Several years ago I signed up for a free tier account with AWS to play with . But I also didn't know what I was going to do with it - I didn't create any resources. Got distracted, a few weeks went by, they sent me an invoice! It wasn't for much, but it was not $0. I was very confused (and never figured out why I was charged). Fortunately I was able to reach customer service and get the costs dropped, and I promptly closed my account so that I didn't accidentally (through no action of my own) accumulate further charges!
I'd like to see "get charged more than expected" or "think you were on the free tier but somehow you weren't" on this purity test.
EDIT: OK either "free tier" was added just now or I fat-fingered "free" when I searched for it earlier :)
The reason I don't like AWS is because billing is always at least like 24 hours behind. By time you realize you don't goofed, the bill's already probably more than you thought.
If you want fixed charges use AWS amplify or another service built on AWS primitives. But the whole reason for using AWS is flexibility and “pay for what you use”.
If you don’t understand what a button does then don’t press it until you understand it?
How would this actually work? Actually think a bit about how hard it would be to add a global, synchronised and immediate view of an accounts cost and check it on every single API call.
Take S3 for example: you set a 1$ limit then concurrently upload 10 1$ per month files. What happens? Should 9 of those uploads fail? How would you ever synchronise that? Or perhaps they complete, but should the bucket delete the contents after the ”storage cost per hour” limit is reached?
Perhaps you could reconcile the account cost usage every hour, and when reached the account should be locked somehow and no new writes or reads can be done on anything. Which is basically breaking the account and everything that runs on it. Most people don’t want that.
How would it even work with bandwidth? You’re serving a file from S3 or EC2 with your 10$ account limit. What happens after you use 10$ bandwidth? Should your accounts external internet connection be cut off? How would you even calculate that cost in real time at scale.
Use your brain. AWS are not stupid. It’s a minefield of complexity that would be super expensive to implement and that benefits nobody. The “if you mess up we will refund you up to 2 times” policy works absolutely fine.
What they could do is pause services immediately that can be paused and then give you grace on services where their billing technology has not caught up with real time. They don't necessarily have to actually stop services if they cannot technically do it instantly, just stop charging you at an agreed amount. That's all that's needed.
“Oh sorry I used 100tb of bandwidth over my 10$ limit, I guess your billing technology has not caught up with real time! Lucky you are so nice and stopped charging me at an agreed amount”.
I would like that.
No button would ever be pushed, and AWS would die as a platform.
Definitely not against advertising the product but make it more explicit
That said, I'm vaguely amused at the concept (I got a 23), but they also misspelled my name (Corey) and the name of the newsletter (Last Week in AWS, not "This Week").
I also have some quibbles about a few of the questions, but that's probably no surprise...
Good to know it’s not just me (but seriously, the way they’ve implemented search in paginated results is the most actively hostile UX decision I’ve ever encountered. It’s so bad it almost makes me feel better about the half-baked hacky stuff I’ve done over the years.)
That said, the redesign made it worse (those scroll windows that don't fill up the pane... MY GOD HOW DO YOU NOT FIX THAT), there is no sense of continual improvement and addition of useful new features and views, performance is pretty bad.
All I ever hear "you're not supposed to use the UI, you're supposed to use the API".
Don't get me started on the API.
This quiz is missing these three key points:
- has culled 1,000$ annual savings in a AWS cost saving review?
- has culled 10,000$ annual savings in an AWS cost saving review?
- has culled 100,000$ ?
- has culled 1,000,000$?
I ... almost .. got to 1,000,000 once.
- trapped AWS support in an outright lie?
- gotten AWS support to tell you results of hidden internal metrics to debug something?
At least it's not the GCP API. Had to use that for some compliance automation once and still have nightmares about it.
The biggest problem with GCP's api/cli/sdk/console is they're not the same. There are things you can only do in the console, or have different grammars across CLI/SDK, or have different permission schemes across them. Add to that the intermixing of "IT Admin" and "Cloud Admin" roles due to all of your Google Groups also being IAM groups, and IAM being somehow tied into your G Suite admin area, it's just a confusing mess.
With AWS, the CLI is the API is the SDK. So if you can use one, you can use all of them very easily.
My gripe is that the thing just gives off this BLOATED impression. Safari routinely reloads it because it was "using significant energy." Every time I load a page I just wait until it renders, goes blank, re-renders, goes blank, places everything that was on the left over to the right, and then finally things settle down and I click a button. That all takes about 1.5s though, so not awful.
Who is the "they" in that sentence? Each AWS product team writes their own console UI, as far as I know, and they're free to do pagination however it makes sense for them.
(Of course my question doesn't really matter because they're all pretty middling.)
And even if they can't change the API, the front-end could request the next page from the API until they have a full page to display.
It's certainly not just you. I've complained about it at work parties at AWS, and so did my colleagues.
I was on a front end team working on the AWS Console for a fairly well known service.
IMO it's a better UI than O365/Azure and I don't have much experience with Gcloud to say much but they seem about equal but still leaning towards AWS as the best UI of the top 3 cloud providers.
If that is your comparison then AWS Console is amazing.
In general tho, AWS Console is OK at best, it does the job and for some services it is actually good. Many services are awful tho.
$0.005 * (1,000,000 PUT operations / 1,000) = $5.00 to write 1GB. The on-going storage cost I believe would be free since the files themselves are empty.
Meanwhile writing a single 1GB file to S3? Costs you $0.023 per month storage, and the single write cost is $0.000005. It'll take 217 months to cost $5.00
They've also raised SNS prices in some markets where regulatory fees increased, boosted pricing for domain registration several times, redid the pricing model for IoT Core when it was in beta, and changed the pricing model for AWS Config in ways that are kinda... unfortunate, for a lot of us.
I’m kidding, point taken. I listen to your podcast all of the time.
You also called a project I was heavily involved in at AWS “This may be the worst AWS naming of 2021.”
I took it as a point of nerd pride. Out of all of our bad naming convention, that said a lot.
I went through an awful period of on-call at my last place, and seeing "Amazon" come through on the work email shocked me awake thinking it's another CloudWatch alert, only to blearily see it was the regular end-of-month statement.
You get the same feeling when you wake up before your alarm and you think you overslept, but now you can't get back to sleep for the adrenaline in the blood.
and you have your own aws account
and the work finance department screws up
and you get an email from aws with a > 100K owed bit of information....
that was a moment of panic.
But it turns out that the Rice Purity Test will be celebrating its 100th anniversary next year. https://lhsepic.com/6806/opinion/3_op_ricepuritypranavm/
> The Rice Purity Test is a survey first administered by Rice University in 1924. The test asks 100 yes-or-no questions to output a numerical score, with 100 being the “most pure” and 0 being completely “impure.” The first test was given only to women in order for Rice to gauge how risqué their female population was. It often resulted in shaming: women with scores below 70 were often viewed as immoral, whereas those with scores above 90 were seen as uptight. The test has since become popular worldwide, despite retaining its most fundamental problem: it reduces test-takers’ complex experiences to a single numerical value.
Side note, I remember finding one of the dirtier purity tests on usenet after I got onto the internet in `91. Just being fresh in college at that point, a few of the terms used were new to me. hahahahah.
Click click click… ouch an 18.
So we were, deep in the shit, fighting fires due to our systems being in a perpetual state of DoS, and we asked if they would rack a machine with a certain overclocked Skylake chip in it. We offered 7 figures to do it. It was worth that much to us to get ~40% more capacity without having to migrate off AWS. They said no :)
Random reflection: Key to AWS costs is to always assume every compute, storage or networking unit incurs cost. Always.
Then got to (a) pricing of the service in question, (b) FAQ of the service, (c) pricing and FAQ for EC2 specifically and scan for every pricing information you can.
If after that you can be 100% sure something does not incur cost, only then you are allowed to remove it from your financial model of what you want to deploy.
You do have a financial model, right?
I thknk there was at least a "geek purity test" and a "programmer purity test".. and maybe a "UNIX purity test"? Not sure. They were all quite funny though (at least my younger self thought so)
Like how-fucking-dare RDS use DNS for failover instead of ARP so it's impossible to do instant non-user-visible recovery.
I've been using AWS at various companies and have tried to embrace its paradigms but I hate them.
You could put a histogram of the results and show where the player is on the histogram.
I'm a little bummed there wasn't a "didn't get covid at re:Invent" option...
https://aws.amazon.com/about-aws/whats-new/2022/04/aws-data-...
I'm sorry, there's a dark mode for the console!?
https://{region}.console.aws.amazon.com/settings/home?region...
Also, for anyone waking up in the middle of the night on billing alert emails, this is why a lot of folks are using https://www.vantage.sh/
We (society) really need to move beyond making these lame jokes. They weren’t funny in the 80’s, 90’s, 00’s, or the 10’s…
b) just because something is common or widespread, doesn't mean it should be normalized or treated as "the best that it can be". That's a highly conservative (in the non-US-political sense) and neophobic viewpoint - not what I would expect on Hacker News. Reduction of a S/O to a sex-provider might be common among certain social groups, but that's not the society I dream of.
Nothing in the joke said "only". By that logic, all single sentences are reductionist.
You're intentionally using emotionally laden words.
Also, the difference between a BFF and an significant other generally is the sex.
> you are (wrongly) assuming that this one person is the only person who dislikes this type of joke
Making everyone happy isn't possible and it's generally not even worth trying because some people just dislike everything. If they're overly dramatic about the "harm" it usually means there isn't any, that they just like controlling discussion.
> just because something is common or widespread, doesn't mean it should be normalized or treated as "the best that it can be"
Nobody did that. They said that in a sense of "and yet you're not dead yet."
Generally humor like this is only bad if it unreasonably hurts someone and "all SOs" are not a class who can be hurt by humor. Nobody is being maligned.
Read your way, yeah, it's inappropriate for a work context.