AWS from Zero: the CLI-only map

Welcome to AWS from Zero. The rule for this series is simple:

We learn AWS through the command line first. The console can explain, but the terminal proves.

That does not mean the AWS Console is bad. It is useful for exploration, diagrams, billing pages, and visual debugging. But when you learn only by clicking, you often miss the API shape underneath. The CLI forces you to see the actual verbs: create, describe, list, put, get, delete.

Why CLI-first?

AWS is huge. The way to make it less scary is to notice the pattern that repeats everywhere.

aws <service> help
aws <service> list-...
aws <service> describe-...
aws <service> create-...
aws <service> update-...
aws <service> delete-...

S3 has buckets and objects. EC2 has instances, images, key pairs, volumes, security groups, and VPC objects. IAM has users, roles, groups, and policies. Different nouns, same API rhythm.

Once you learn that rhythm, a new AWS service becomes less like a new planet and more like a new neighborhood.

The series contract

This is not a 10-part course. It is the beginning of a long CLI-first AWS library. The first posts build the foundation; after that, each service can split into many small lessons, variations, mistakes, fixes, and mini projects.

Every lesson will try to be small enough to finish in one sitting.

• Start with the minimum concept.
• Run one or two safe commands.
• Inspect the result.
• Make one tiny variation.
• Clean up anything that may cost money.

We will avoid production shortcuts early. If something is dangerous, expensive, or easy to misunderstand, I will say so before the command.

Foundation batch: the first 10 lessons

Think of this first batch as ten small steps that build one foundation:

1. Map: what AWS is, why CLI-first, and how this series grows.
2. Setup: install AWS CLI, configure a profile, and prove identity.
3. Command shape: help pages, output formats, JSON, filters, and queries.
4. Identity: IAM users, roles, policies, MFA concepts, and least privilege.
5. Safety: budgets, billing alerts, regions, naming, and cleanup habits.
6. S3 basics: buckets, objects, upload, download, sync, and deletion.
7. S3 website: static hosting through CLI-only commands.
8. EC2 basics: key pair, security group, instance launch, SSH, and cleanup.
9. Networking: VPC, subnets, routes, internet gateway, and security groups.
10. Automation: repeatable scripts, JSON inputs, CloudFormation, and the long roadmap.

These are not the whole AWS universe. They are only the base layer. After this, the series can grow into databases, containers, serverless, analytics, AI/ML, security, governance, migration, specialized services, and every small CLI variation that deserves its own clear explanation.

What you need before part 2

You need a terminal, an AWS account, and a willingness to copy commands slowly instead of blindly.

Use your own account only if you are comfortable managing costs. If you are learning inside a company account, follow your organization's access rules.

In part 2, we install and configure the AWS CLI, then run the most important first command in AWS:

aws sts get-caller-identity

That command answers the beginner question that never stops being useful: who am I in AWS right now?