AWS can feel overwhelming at first — 200+ services, a confusing console, and a billing model that seems designed to surprise you. But you don't need all of it. This guide cuts through the noise and walks you through the handful of services that actually matter when you're starting out. By the end, you'll have a real app running in the cloud. ## Step 1 — Create Your AWS Account Head to aws.amazon.com and sign up. You'll need a credit card, but AWS has a generous Free Tier that covers most beginner workloads for 12 months. Once you're in, do these three things immediately. - **Enable MFA on the root account** — Go to IAM → Security credentials → Assign MFA. Use an authenticator app. Never use root credentials for day-to-day work. - **Set a billing alarm** — Go to CloudWatch → Alarms → Create Alarm → Billing. Set a threshold like $5 so you get an email before any surprise charges. - **Create an IAM user** — Go to IAM → Users → Add user. Give it AdministratorAccess and use this for everything. Log out of root, log in as your IAM user. ## Step 2 — Install & Configure the AWS CLI The AWS Management Console is fine for exploring, but the CLI is how you get real work done. Install it, then wire it up with your IAM credentials. ```bash # macOS (Homebrew) brew install awscli # Ubuntu / Debian sudo apt install awscli -y # Windows (PowerShell — run as Admin) winget install Amazon.AWSCLI ``` After installing, run `aws configure`. You'll need your Access Key ID and Secret Access Key from the IAM console (IAM → Users → your user → Security credentials → Create access key). ```bash aws configure # You'll be prompted for: # AWS Access Key ID: AKIA... # AWS Secret Access Key: xxxxxxxxxxxxxxxx # Default region name: us-east-1 # Default output format: json ``` Verify it's working by listing your S3 buckets — you should get an empty list, not an error. ```bash aws s3 ls # Expected output: (nothing — or your buckets if you have some) # If you see "Unable to locate cre