Skip to main content
Cloud Computing

AWS Tutorial with Examples.

AWS tutorial for beginners: EC2, S3, Lambda, IAM, VPC, RDS and the core cloud architecture patterns of Amazon Web Services.

Architecture at a glance

Click any box to open the lesson that teaches it

AWS architecture at a glance

CLI → IAM → VPC → EC2 / Lambda → S3 / RDS, watched by CloudWatch

AWS architecture at a glance An AWS CLI call runs as an IAM identity restricted to a policy. Compute lives inside a VPC's subnets, route tables and security groups: EC2 for servers you manage, Lambda for serverless functions. Both call S3 for object storage and RDS for a managed database. CloudFormation provisions the whole stack as one template and CloudWatch watches it with metrics, logs and alarms, with Cost Explorer and the Well-Architected Framework's six pillars as the final check. AWS CLI region · CLI IAM users · roles VPC subnet · SG EC2 security group Lambda serverless Data S3 buckets · objects RDS managed Postgres Watches & provisions CloudFormation stack · template CloudWatch metrics · alarms Cost & reliability Cost & Well-Architected Cost Explorer · pillars
How it fits together (5 steps)
  1. Every request starts from the AWS CLI, configured for a region and confirmed against an identity before anything else runs — against LocalStack with zero account, or against real AWS once credentials are set.
  2. That identity is only as powerful as its IAM policy: a user with no permissions gets a real AccessDenied until a least-privilege policy is attached — roles skip the long-lived keys entirely.
  3. Compute runs inside a VPC, where a subnet only reaches the internet once its route table points at an internet gateway, independently of whatever its security group allows — both have to be right. EC2 launches an instance there you SSH into directly; Lambda runs the same code with no server to manage, at the cost of a cold start on the first invocation.
  4. Both call the data layer: S3 holds objects in a versioned bucket, and RDS runs a managed Postgres instance you can snapshot and restore.
  5. Two services wrap the whole stack: CloudFormation deploys every resource above as one template that rolls back together on failure, and CloudWatch collects the metrics, logs, and alarms that watch it while it runs. Cost Explorer and the Well-Architected Framework's six pillars are the last check before calling it production-ready.

Beginner

Start here — no prior experience needed

4 lessons

Intermediate

For developers with core concepts down

5 lessons

Advanced

Production-grade patterns for experienced engineers

1 lesson

Also part of AWS

Taught in other topics. Each link opens the lesson in its home topic.

3 lessons