A brief introduction to the services on offer from Amazon Web Services (AWS) – perfect for people who are beginning their certification journey!
I’ve not long passed my “AWS Certified Solutions Architect — Associate” exam (that’s a mouthful), and whilst I was studying for it I noticed that, a lot of the service names are “odd”. Or acronyms. Or Greek. I’ve covered this sort of topic before, (see: here), so I thought I’d do it again, with a similar level of brevity. And snark.
There are a lot of services available, so for the sake of my own sanity, I’m not covering them all. Also, Amazon has a habit of releasing new services quicker than the drink runs out at an open bar, making it highly likely another few will turn up whilst I’m writing this.
Also worth noting, just by reading this you WON’T pass the “AWS-SA-Assoc” exam as there aren’t any questions about what the names mean. It’s more about how you use the services.
Yep. Starting here. AWS is an acronym (and there’s a lot of them coming up) for Amazon Web Services. But you probably already knew that. A word of warning, a lot of the names are about this creative. le sigh.
Fun(?) fact, AWS made up 58% of Amazons’ profit in 2018 (source: https://www.investopedia.com/how-amazon-makes-money-4587523). So you can feel better about all the money you’ve spent on Amazon. At least that’s what I’m clinging to.
The Starting Tools
OK. Seems like a good place to start. Well, re-start. These are the tools that AWS is most known for. It’s probably where you’re going to get started with it too.
Elastic Compute Cluster. Yep. Gonna need to define that one a bit.
In this sense “Elastic” is not that far from an elastic band. The capacity of your resources can stretch and shrink to meet demand, within limits. Compute is running apps, although in this case it refers to virtual servers. Cluster means there’s more than one.
Simple Storage Service. It’s got 3 S’s, so S3. This is an object store, rather than a file store (though Amazon does have one of those too). It’s interchangeable with file storage to an extent. But instead of using native OS commands you interact with it using the AWS CLI tool. Yes I know, more acronyms.
Virtual Private Cloud.
To understand this you need to understand the difference between public and private cloud. The short version is “with private cloud you own it all, and are the only person (or company) on the hardware. With public cloud, none of that is true (in most cases, but I’m not going to go into that here).
A VPC allows you to treat AWS as if it’s all yours. You’re not going to see anyone else’s resources when you log in, and they won’t ever see any of yours either.
For the most part in AWS you have no idea that anyone else is using the service, except for a few unique naming rules.
DNS (I’m sorry, I’m at it again), Amazon style.
Domain Name System is a translator, between human readable web addresses and an IP address. For example www.google.co.uk has an ip of 184.108.40.206 which your PC uses on the internet (yes that is actually google.co.uk’s IP). Route53 is Amazons implementation.
It’s named after 2 things. Route66 was the first highway in the U.S.A., and DNS servers work on port 53. Kinda creative I guess?
You can “watch” your “cloud” resources. CloudWatch. This covers metrics and logs, but there are different charges depending on what you’re looking at.
You can do some cool stuff with logs, like exporting them to other tools for analytics and graphing.
Auditing. Well, an audit “trail” on your “cloud”. Same sort of naming convention here.
Elastic Block Store.
This is virtual disk, but it’s a type of disk suited to reading and writing in “blocks”. Databases tend to use this sort of storage type, as it has a much faster read & write speed.
Relational Database Service.
Amazon will set up and manage a “Highly Available” (HA) cluster of a database engine of your choice. Not all DBMS’s are available (sorry Sybase users), but the common ones are there.
You still get CLi and SSH access too, which is nice if you need/want/like to fine-tune anything.
You can pretty much use this as a drop-in replacement for an on-premises DB cluster, but you can’t quite do without a DBA. You will also need some EBS (see above).
Identity Access Management (what?)
This is AWS’s “permissions” setup. It’s a way to control who gets access to what. Broken down into users, groups, roles & policies. Users go into groups. Roles can be applied to groups or users. Policies are attached to roles.
The upshot of this, is servers/other resources can hold an “IAM Role”. This allows them access to do/see/get/change something from another service, without having to create service accounts. If you’ve ever used them in the past, you’ll understand why this is “A Good Thing TM”.
Elastic File Store.
Basically a network drive. Cool pricing model — you just use it, and pay for what you use. Unlike disk-based storage pricing, where you have provision and pay for a whole disk. One less headache.
Phew. Time for a break. Actually please don’t leave. It gets better I promise.
Have a coffee. On me.
The Intermediate Tools
These are tools that you will use a lot, once you’re over the initial “what’s this cloud thing?” hurdle. If you’re lucky, you’ll skip the hurdle and crack right on with these too.
ECS & ECR
Elastic Container Service & Elastic Container Registry.
Right, containers. They’d come up eventually.
ECS is Amazon’s service for orchestrating Docker containers (sort of Amazon’s take on Docker Swarm I guess?). ECR is their version of Docker Hub, so you can store all your Docker images inside AWS. Great if your InfoSec people don’t like the idea of data leaving controlled environments.
Simple Queue Service
It’s a queuing service. Don’t really know what else to say about it? Nothing creative about the name. It was AWS’s first available service though, way back in 2004, predating AWS itself by 2 YEARS!
OK, that’s interesting.
SNS & SES
Simple Notification Service & Simple Email Service
It sends notifications (think text messages), and emails. This is sort of writing itself at this point.
SNS will send emails, but SES gives you more control over the email content.
Aurora & DynamoDB
Aurora is part of the RDS family, but is fully managed, so you don’t get access to the underlying servers. It’s both MySQL and PostgreSQL compliant. Either/or, not both at the same time. The name is Latin for “dawn”.
A little bit of mental gymnastics here, but maybe they mean “dawn of a new database technology”?
DynamoDB is the next extension of AWS’s DB offering. Dynamo is a NoSQL (Not Only SQL) database. It’s largely cheaper to run than RDS/Aurora, and is fully serverless, but doesn’t enforce referential integrity (see here for an explanation). So if you can work with that (and being honest, you probably can) go for DynamoDB.
The name is a derivative of the storage system Dynamo (reference). This, in turn, is probably based on a physical dynamo, which turns kinetic energy (rotation) into electricity. I can’t work the link out, but it sounds cool
AWS has two offerings for caching services, both under the banner of Elasticache. Redis and Memcached. There are reasons why you’d use one over the other, but I’m not going to go into that here (use Redis if you value your sanity). Again a fairly traceable name. Cache because it’s a cache, elastic because it implements elasticity in the same way the EC2 service does.
This is AWS’s data warehousing solution, using columnar storage (most DB’s are row-based, with the notable exception of SybaseIQ. Take 10 imaginary points if you’ve heard of that before).
The name is based on one of 2 things, and I can’t find anything definitive to confirm either.
Option 1: Redshift is a physical phenomenon, and part of the doppler effect, where items getting further away appear red. This is usually due to expansion, so this could be the easy way you can expand the size of your redshift clusters.
Option 2: It’s a swipe at Oracle, who have a red logo. The idea being that teams would shift away from Oracle.
Take your pick which you believe. I think option 2 is more likely, but because I’m a nerd I like option 1 more.
This really dry name sits in front of a really useful tool (isn’t that always the way?). The well-architected tool is AWS’s attempt to automate some of the work their consultants were doing with their customers. Particularly around how best to setup their infrastructure against the well-architected framework:
The More Obscure (But Still On The Exam).
Kinesis & Firehose
Snowball & Snowmobile