AWS Core Services You Actually Need to Know as a Cloud Engineer

AWS has over 200 services. The AWS console has so many icons it looks like a phone screen from 2008. This overwhelms most beginners — and it's exactly what leads to the Shiny Object Trap.

The truth? Cloud engineers use about 15-20 services regularly. Based on our analysis of 1,000+ cloud job postings, here are the services that actually appear in job descriptions and interview questions.

Compute: EC2 and Lambda

EC2 (Elastic Compute Cloud) is the foundation of AWS. It's a virtual server in the cloud. You need to understand instance types, AMIs, security groups, key pairs, Elastic IPs, and Auto Scaling Groups. Every cloud engineer uses EC2.

Lambda is serverless computing — you write code, upload it, and AWS runs it without you managing any servers. You need to understand triggers, execution limits, environment variables, and common use cases (API backends, file processing, scheduled tasks).

Key interview question: "When would you use EC2 vs Lambda?" Answer: EC2 for long-running, stateful applications with predictable traffic. Lambda for event-driven, short-duration tasks with variable traffic.

Storage: S3 and EBS

S3 (Simple Storage Service) is object storage — files, images, backups, static websites. You need to know: bucket policies, versioning, lifecycle rules, storage classes (Standard, IA, Glacier), encryption, and static website hosting.

EBS (Elastic Block Store) is block storage attached to EC2 instances — your server's hard drive. Know the volume types (gp3, io2, st1), snapshots for backups, and encryption.

Pro tip: S3 is used in almost every AWS architecture. Master it deeply. Knowing S3 bucket policies, cross-region replication, and event notifications sets you apart.

Database: RDS and DynamoDB

RDS (Relational Database Service) is managed PostgreSQL, MySQL, SQL Server, or Aurora. You need to understand Multi-AZ deployments, read replicas, automated backups, and subnet groups (databases go in private subnets).

DynamoDB is a managed NoSQL database. Know when to use it (high-speed reads/writes, simple key-value lookups) vs RDS (complex queries, relationships between data).

Networking: VPC, Route 53, CloudFront, ELB

VPC — we covered this in the networking guide. Subnets, route tables, security groups, NAT Gateways.

Route 53 — DNS management. A records, CNAME records, routing policies (simple, weighted, failover).

CloudFront — CDN (Content Delivery Network). Caches your content at edge locations worldwide for faster delivery. Used with S3 for static sites and ALB for dynamic content.

ELB (Elastic Load Balancing) — Application Load Balancer and Network Load Balancer. Traffic distribution, health checks, SSL termination.

Security: IAM and KMS

IAM (Identity and Access Management) is the most important security service in AWS. Understand: users, groups, roles, policies, the principle of least privilege, and cross-account access. Every AWS resource interaction is governed by IAM.

KMS (Key Management Service) — encryption key management. Used to encrypt S3 buckets, EBS volumes, RDS databases, and more.

Security is not optional. In interviews, always mention security — put databases in private subnets, use IAM roles instead of access keys, encrypt data at rest and in transit. This shows maturity.

Monitoring: CloudWatch and CloudTrail

CloudWatch — metrics, logs, alarms, dashboards. Know how to create alarms for CPU usage, set up log groups, and build basic dashboards.

CloudTrail — audit logging. Records every API call made in your AWS account. Essential for security and compliance.

Containers: ECS, ECR, and Fargate

ECS (Elastic Container Service) — runs Docker containers on AWS. Fargate is the serverless compute engine for ECS — no EC2 instances to manage. ECR (Elastic Container Registry) stores your Docker images.

Containers are increasingly important in cloud engineering. You don't need to be a Kubernetes expert to start, but you should understand Docker basics and be able to deploy a containerized app on ECS/Fargate.

How to Learn These Services

Don't study services in isolation. Build a project that uses multiple services together:

1. Week 1-2: Build a static website on S3 + CloudFront + Route 53
2. Week 3-4: Build a dynamic app with EC2 + RDS + ALB in a VPC
3. Week 5-6: Build a serverless API with Lambda + DynamoDB + API Gateway
4. Week 7-8: Containerize an app and deploy on ECS Fargate

Each project teaches you multiple services in context. By the end, you'll have four portfolio projects and deep knowledge of the 15-20 services that actually matter for getting hired.