DEV Community

Aditya Singh
Aditya Singh

Posted on

AWS for Developers: The Services You Actually Need to Know (Beginner-> Production)

#devops #career #beginners #productivity

Most freshers start learning cloud by randomly exploring services.

That’s the wrong mental model.

AWS is not a list of tools.
It’s a system architecture.

Once you understand how services connect, cloud stops being confusing.

Here’s a developer-first breakdown of the most commonly used AWS services, their use cases, and what works together in production systems.

🌐 1. Entry Layer — How Users Reach Your System

These services sit at the edge of your architecture.

Route 53

What it is:
AWS DNS service.

Use case

  • Map domain → AWS resources
  • Route traffic globally

Example:

myapp.com → Load Balancer / CloudFront
Enter fullscreen mode Exit fullscreen mode

CloudFront

What it is:
Content Delivery Network (CDN)

Best for

  • Static websites
  • Media delivery
  • Reducing latency worldwide

Common combo

CloudFront + S3
Enter fullscreen mode Exit fullscreen mode

Example architecture

User → CloudFront → S3 (static site)
Enter fullscreen mode Exit fullscreen mode

AWS WAF + Shield

Purpose: Security layer

WAF protects against:

  • SQL injection
  • XSS
  • malicious traffic

Shield protects against:

  • DDoS attacks

Used with

CloudFront
Load Balancer
API Gateway
Enter fullscreen mode Exit fullscreen mode

⚙️ 2. API Layer — Where Requests Enter Your Backend

Load Balancer (ALB)

Purpose
Distributes traffic across servers.

Example

User → Load Balancer → EC2 instances
Enter fullscreen mode Exit fullscreen mode

Best when

  • Running backend servers
  • High traffic systems

API Gateway

Purpose
Serverless API management.

Best for

  • Microservices
  • Lambda backends
  • Mobile apps

Example

Client → API Gateway → Lambda → Database
Enter fullscreen mode Exit fullscreen mode

🖥️ 3. Compute Layer — Where Your Code Runs

This is where developers spend most time.

EC2

What it is
Virtual machines in the cloud.

Best for

  • Full control servers
  • Custom backend apps

Example

Node.js / Spring Boot / Python backend
Enter fullscreen mode Exit fullscreen mode

ECS (Elastic Container Service)

Purpose
Run Docker containers

Best for

  • Microservices
  • containerized apps

Fargate

Serverless containers

You run containers without managing servers.

ECS + Fargate
Enter fullscreen mode Exit fullscreen mode

Very common in production.

EKS

Managed Kubernetes on AWS.

Best when:

  • Large microservice systems
  • DevOps teams using Kubernetes

Lambda

Serverless compute.

You upload functions.

AWS runs them automatically.

Best for

  • event processing
  • APIs
  • automation

Example

API Gateway → Lambda → DynamoDB
Enter fullscreen mode Exit fullscreen mode

🗄️ 4. Storage & Databases

Every application needs storage.

S3 (Simple Storage Service)

Most used AWS service.

Best for

  • static files
  • backups
  • data lakes
  • ML datasets

Example

CloudFront → S3 → Static website
Enter fullscreen mode Exit fullscreen mode

RDS

Managed relational database.

Supports:

  • MySQL
  • PostgreSQL
  • MariaDB

Best for

Traditional backend apps
Enter fullscreen mode Exit fullscreen mode

Example

Spring Boot → RDS (PostgreSQL)
Enter fullscreen mode Exit fullscreen mode

Aurora

AWS optimized database.

Better performance than standard RDS.

Used by:

  • high scale apps
  • SaaS platforms

DynamoDB

NoSQL database.

Best for

  • serverless architectures
  • high scale systems

Example

Lambda → DynamoDB
Enter fullscreen mode Exit fullscreen mode

OpenSearch

Search and analytics engine.

Used for:

  • logs
  • search systems
  • monitoring dashboards

⚡ 5. Application Coordination (Microservice Communication)

Modern systems need async communication.

SNS

Pub/Sub messaging.

Example

Order created → SNS → multiple services notified
Enter fullscreen mode Exit fullscreen mode

SQS

Message queue.

Used to decouple services.

Example

API → SQS → Worker service processes jobs
Enter fullscreen mode Exit fullscreen mode

EventBridge

Event routing system.

Great for event-driven architectures.

Step Functions

Workflow orchestration.

Example

Upload → Process → Store → Notify
Enter fullscreen mode Exit fullscreen mode

📊 6. Data Processing & Analytics

Used in data engineering pipelines.

EMR

Big data processing.

Runs:

  • Spark
  • Hadoop

Athena

Run SQL queries directly on S3 data.

Example

Logs in S3 → Query with Athena
Enter fullscreen mode Exit fullscreen mode

Glue

Data pipeline service.

Used for:

ETL jobs
data cataloging
Enter fullscreen mode Exit fullscreen mode

Redshift

AWS data warehouse.

Used for:

analytics dashboards
BI tools
Enter fullscreen mode Exit fullscreen mode

🤖 7. AI Services

AWS also offers ready AI tools.

SageMaker

Build and deploy ML models.

Bedrock

Access foundation models.

Used for:

  • AI applications
  • LLM powered products

Rekognition

Computer vision.

Example

Image → Detect objects/faces
Enter fullscreen mode Exit fullscreen mode

Transcribe

Speech → text.

Polly

Text → speech.

⚙️ 8. DevOps + Infrastructure

CloudFormation / CDK

Infrastructure as Code.

Define cloud resources using:

  • YAML
  • TypeScript
  • Python

CodePipeline

CI/CD automation.

Pipeline example

Git push
   ↓
CodeBuild
   ↓
CodeDeploy
   ↓
Production
Enter fullscreen mode Exit fullscreen mode

📈 9. Monitoring & Observability

CloudWatch

Logs + metrics.

Used to monitor:

  • servers
  • APIs
  • Lambda

X-Ray

Distributed tracing.

Helps debug microservices.

🧠 Example Production Architecture

A common modern backend architecture looks like this:

User
 ↓
Route53
 ↓
CloudFront
 ↓
API Gateway
 ↓
Lambda / ECS
 ↓
DynamoDB / RDS
 ↓
S3 Storage
Enter fullscreen mode Exit fullscreen mode

With background jobs:

Service → SQS → Worker → Database
Enter fullscreen mode Exit fullscreen mode

Monitoring:

CloudWatch + X-Ray
Enter fullscreen mode Exit fullscreen mode

🚀 Advice for Freshers Learning AWS

Don’t try to learn 200 services.

Focus on the core stack first.

Start with:

1️⃣ S3
2️⃣ EC2
3️⃣ RDS
4️⃣ Lambda
5️⃣ API Gateway
6️⃣ CloudFront
7️⃣ DynamoDB
8️⃣ CloudWatch

That alone covers 80% of real-world architectures.

💡 Final Thought

Cloud engineering is not about knowing every service.

It’s about understanding how systems connect.

Once you see AWS as a system design toolkit, everything becomes much easier.

If you're a developer entering cloud:

Learn architecture, not just services.

That’s the difference between
someone who uses AWS
and
someone who designs systems on AWS.

Top comments (0)