It's possibly a sign that you are a good engineer. If you are using infrastructure-as-code, whether that is terraform or cloudformation, you are used to looking at a yaml or json file that does not include icons. If you have automated everything to the point that you rarely need to log into the AWS console, you probably don't regularly see these icons.
The only reason I can play this game is because "Icons with Labels" is impossible to deal with in the AWS console. I _really_ wish I could just set the labels myself.
"AWS Simple Email Service." Were you worried I would forget it's an AWS service? Or worried that I wouldn't remember it's simple, or a service? Do you offer any other email service? Can I please just rename the label to "SES"?
and then there's "flip a coin" about whether it's "AWS Foo" or "Amazon Foo". I think I once read that Amazon Foos were things that were used internally, too, and AWS Foos were things only sold to pay for rocket fuel and yachts (I kid, I kid; paying for all those Graviton fabs is some serious $$$ too)
You surprised me for a second and I thought you had found an example of where they actually _wrote out_ Amazon Web Services in the title of something and I was going to claim they must get paid by the letter or something, but no, it's just "AWS Systems Manager ..." https://docs.aws.amazon.com/systems-manager/latest/userguide...
It makes me wonder too how many of these actually _are_ the "it's like". For example, I know that Elasticache actually is redis or memcached... makes me wonder if Kinesis isn't actually Kafka rebranded.
It's not. Kinesis was around before Kafka became the de-facto tool for data streaming. AWS has a separate managed Kafka service called MSK, which came much later.
I guess the point is not that other companies also have products with unrelated names, but if you happen to be familiar with Y then saying "Amazon x is just Amazon's version of Y" is very succinct.
Same. Though, I forget what it is since I heard about it. Now I think it's funny that it could refer to either cruel bureaucracy or turning into a bug.
Most of these are really funny, but I feel like they should have just left out the reasonable ones. There's enough of them that it kind of kills the humor after a certain amount of "actually this one is fine" imo.
I have red green color blindness (deuteranopia) and i have no idea if my answer is right or wrong on until i change my monitor settings to high saturation. (I usually turn that off because it messes a lot with other colors)
Oh hell I have spent the last decade working with AWS and I still have no idea what any of the icons are. They are all complete shit. Literally the worst.
To be fair I can't remember half the product names other than the core ones either. Elastic Banana or whatever. Maybe Dynamo Donkey. I just don't know any more.
Edit: I'm also an AWS Architect Professional or whatever it's called now. Shows how a monkey can pass the certs eh?
3/20 and two correct ones were guesses here; I was actually wondering what's wrong with me, asking "Dude, have you ever even seen the AWS console at this point?" (I have in fact stared at it way too much). Goes to show a lot of these icons just aren't very distinctive and don't seem to matter much.
Worth noting that also from experience that applies to the amount of effort they put into services. Most of the non-core ancillary services are buggy garbage. I'm wondering if we're going to cause an integer overflow on the support ticket system the way we're going.
To be fair, the majority of professional interaction with AWS should be via text interfaces - infrastructure as code, SDKs, commandline - where icons don't matter.
The names aren't often all that much better, of course
GCP has a mix of "that makes sense" (scheduler, run, compute, spanner) to "I can see where they were going" (memorystore, speech) with a smidge of: "that doesn't make any sense/just a fun design that isn't meaningful" (anthos).
Lots of icons are dots or squares that are connected, which of course isn't helpful because that's what nodes in a network actually are in all circumstances.
GCP is (un)fortunately saved by it's relatively low product offering (by AWS's standards at least).
Where do these icons come from they don't match what's used in the AWS console at all.
So many of these are weird because I mostly know of their icons from the main console page which apparently doesn't match the ones this quiz is pulling from because it said the S3 icon isn't green and the IAM icon is a key. In the console it's green and an ID with a lock icon on it at least for me.
Ah ok. I've never used designer much at all so the fact they didn't match the AWS console version of things was really confusing. The first question is the 3 overlapping boxes with a play button which is supposedly the lambda icon but the console just has an orange box with a boxy white λ so I was never going to get that.
Wonder if OP could make a version of this that uses the console icons instead of the designer icons..
I think they may be an older AWS icon set. I was just doing making an infrastructure diagram in lucid chart and the S3 icon was red and I recognized it so I got it right, but it doesn't match whats in the console now
The other person has it right. It's the icon set used in Cloudformation Designer. Which doesn't even match their current icon asset packet for Powerpoint, those generally seem to use the ones used in the console from my limited survey.
I've contributed and/or led development on at least 4 different AWS consoles and have used AWS every day for the last 10 years, with 8 of those working at AWS. Still only got 6 right on the quiz.
That said, AWS is transitioning away from those 3D logos. I just wish they'd transition away from Amazon vs AWS name prefix confusion. I've read the internal notes on why they do that, but the reasoning never clicked for me and I still have no idea without looking it up.
Should they even have any icons? Most of them don't really convey meaning, and there are so many, and many similar (rectangular prisms in different orientations), that it's impossible to remember them.
They need icons so that the utterly incomprehensible architecture diagrams that mostly would convey little useful information even if you recognized the symbols drawn by architects for administrative rather than technical reasons have the façade of a standardized, consistent language.
If you pass this, a team of medical professionals will be sent to your home to peacefully euthanize you, as it is the only ethical choice to end your suffering.
Kind of. It's only supported via an embedded Lambda code block written in a version of NodeJS that will expire in about two months.
Also, please exercise caution with your targets file. We have had a few customers complain that it's easy to mix up your targets list with a customer database dump in S3, in which case it will alphabetically and systematically begin killing them off. This is particularly bad as there's a delay before each transaction hits the AWS billing API, which may result in unusually high costs for the month and/or delays until your bill warning alerts fire.
175 comments
[ 2.9 ms ] story [ 213 ms ] thread"AWS Simple Email Service." Were you worried I would forget it's an AWS service? Or worried that I wouldn't remember it's simple, or a service? Do you offer any other email service? Can I please just rename the label to "SES"?
First world cloud console problems, I guess.
Still, yes, a good r/TitleGore find there :-D
Amazon DynamoDB, Amazon S3, Amazon Chime etc. vs AWS CloudFormation, AWS CodeCommit etc.
AWS WorkMail is a (different kind of) email services, and AWS Simple Notification Service has email delivery functionality. So, yes?
Honestly, it’s not just the icons but the names as well. A lot of them are completely unrelated to the product and make no sense
But my goodness, what an exception....
> Amazon EC2 Queue
Nothing to do with EC2 but okay.
More like Amazon Distributed Functions.
API Gateway
Should have been called: API Proxy
It's like: 3Scale
SNS
Should have been called: Amazon Messenger
It's like: UrbanAirship, Twilio
Kinesis
Should have been called: Amazon High-Throughput
It's like: Kafka
(It always gets me that someone actually named a large software product "Kafka".)
Same. Though, I forget what it is since I heard about it. Now I think it's funny that it could refer to either cruel bureaucracy or turning into a bug.
I use a variety of AWS services every day. I actually got a higher score than I was expecting.
To be fair I can't remember half the product names other than the core ones either. Elastic Banana or whatever. Maybe Dynamo Donkey. I just don't know any more.
Edit: I'm also an AWS Architect Professional or whatever it's called now. Shows how a monkey can pass the certs eh?
Edit: nope, I have no idea. I forgot the number of options and type of questions varies quite a bit.
Shockingly, one of those I got right was "select 4 out of 6".
The names aren't often all that much better, of course
Is it as bad as the "Google" folder on an android?
Lots of icons are dots or squares that are connected, which of course isn't helpful because that's what nodes in a network actually are in all circumstances.
GCP is (un)fortunately saved by it's relatively low product offering (by AWS's standards at least).
So many of these are weird because I mostly know of their icons from the main console page which apparently doesn't match the ones this quiz is pulling from because it said the S3 icon isn't green and the IAM icon is a key. In the console it's green and an ID with a lock icon on it at least for me.
Wonder if OP could make a version of this that uses the console icons instead of the designer icons..
https://aws.amazon.com/architecture/icons/
That said, AWS is transitioning away from those 3D logos. I just wish they'd transition away from Amazon vs AWS name prefix confusion. I've read the internal notes on why they do that, but the reasoning never clicked for me and I still have no idea without looking it up.
Amazon = things that can be used independently.
I.E, Amazon Simple Email Service, AWS CloudFormation
Also, please exercise caution with your targets file. We have had a few customers complain that it's easy to mix up your targets list with a customer database dump in S3, in which case it will alphabetically and systematically begin killing them off. This is particularly bad as there's a delay before each transaction hits the AWS billing API, which may result in unusually high costs for the month and/or delays until your bill warning alerts fire.
From time to time they let it run loose to clean up their products.