Introduction to AWS
Amazon Web Services (AWS) is the largest cloud platform. A few core services cover most applications, and a safe account setup protects you from surprise bills and break-ins.
On this page · 5 min · Beginner
On this page
- Learning objectives
- Explanation
- Code example
- Step by step
- Real-world use
- Common mistakes
- Best practices
- Remember this
- Practice exercise
- Mini quiz
- Related topics
- My notes
- Reading time
- 5 min
- Difficulty
- Beginner
- Updated
- Oct 29, 2026
Related tutorials
Learning objectives#
- Name the core AWS service categories
- Secure a new account (MFA, no root usage, budget)
- Install and configure the AWS CLI
- Understand the free tier
Explanation#
Core services: compute (EC2, Lambda, ECS), storage (S3), databases (RDS, DynamoDB), networking (VPC, Route 53, CloudFront), identity (IAM) and monitoring (CloudWatch).
The root user (the email you signed up with) can do anything, including closing the account. Protect it with MFA, then do daily work with IAM Identity Center users or IAM roles.
The AWS CLI lets you script everything. Configure it with temporary credentials from IAM Identity Center using aws configure sso.
New accounts get a free tier, but many services bill as soon as you exceed it. Create a budget alert immediately.
Code example: Setting up the AWS CLI#
aws configure sso # sign in through IAM Identity Center (temporary credentials)
aws sts get-caller-identity --profile dev
aws s3 ls --profile dev
aws configure set region ap-south-1 --profile dev # Mumbai
{
"UserId": "AROAXXXXXXXXXXXX:asha",
"Account": "123456789012",
"Arn": "arn:aws:sts::123456789012:assumed-role/AWSReservedSSO_Developer_abc/asha"
}This example is illustrative. Copy or download it and run it in your own environment; the expected output is shown above.
Step-by-step explanation#
- configure sso stores a profile that fetches short-lived credentials.
- get-caller-identity confirms which account and role you are using — the AWS equivalent of “whoami”.
- Every command can target a profile and region.
Real-world use case#
A developer uses separate CLI profiles for dev and prod accounts, so a command can never accidentally hit production.
Common mistakes#
If root credentials leak, the whole account is lost. Lock root away with MFA.
Keys in ~/.aws/credentials are frequently leaked via Git. Prefer SSO and roles with temporary credentials.
Best practices#
- Enable MFA on root and every user
- Use IAM Identity Center for people
- Create a budget with email alerts on day one
- Pick one region for learning and stick to it
Remember this#
Root = emergency only. MFA on.
aws sts get-caller-identity = “who am I?”
Budget alert before your first resource.
Practice exercise#
Your task: Create a monthly cost budget of USD 10 that emails you at 80% of actual spend.
Show solution
Console → Billing and Cost Management → Budgets → Create budget → Cost budget
Amount: 10 USD, monthly → Alert: 80% of actual → your email
Mini quiz#
Which command shows the identity your CLI is using?
Want more? Practise all AWS MCQs · AWS interview questions
My notes#
Saved in this browser.