DEV Community

1suleyman
1suleyman

Posted on

⚖️ Traffic Routing and Auto Scaling on AWS (The Easy Way With ELB + EC2 Auto Scaling)

#aws #cloud #beginners #documentation

Hey everyone 👋

If you're diving into cloud architecture on AWS, you’ve probably heard about Elastic Load Balancing and Auto Scaling — and maybe felt a bit overwhelmed. That was me at first too.

But once I walked through the flow and saw it in action, it finally clicked — and now I’m here to break it down for you like I wish someone had done for me 👇

🧸 Think of ELB + Auto Scaling Like a Restaurant Host + Backup Chefs

Let’s say you run a busy restaurant. Every guest walks in and the host decides which table (server) to send them to — that’s your load balancer.

Now imagine some days are busier than others. On slow days, 2 chefs can handle the kitchen. On weekends? You need 4. Do you want to manually call them every time? Nope. You want an automatic system that brings in more chefs when orders spike — that’s EC2 Auto Scaling.

🛣️ What Is Elastic Load Balancing (ELB)?

ELB is AWS’s traffic director. It sits in front of your app and distributes incoming traffic across multiple EC2 instances (or containers, IPs, Lambda, etc).

🚦 Think of it like:

  • Checking which backend is healthy ✅
  • Spreading traffic evenly ⚖️
  • Auto-scaling with your app 💪

There are 3 types:

  • ALB (Application Load Balancer) – For HTTP/HTTPS traffic, operates at Layer 7.
  • NLB (Network Load Balancer) – For TCP/UDP, super fast at Layer 4.
  • GLB (Gateway Load Balancer) – For routing traffic to third-party appliances (e.g. firewalls).

For web apps, ALB is usually your go-to.

🔗 ELB + Listener + Target Group = Your Routing Engine

Here’s what makes ALB work:

  1. Listener – Listens for traffic on a port (like 80 or 443)
  2. Target Group – A group of EC2 instances that will handle requests
  3. Rules – Define how to route traffic (e.g. send /api to one group, /info to another)

💡 Bonus: ALBs also support path-based routing, fixed responses, and even authentication before traffic hits your backend!

⚙️ What Is EC2 Auto Scaling?

Auto Scaling = "Add more EC2s when you’re busy, remove them when you’re not."

It keeps your app:

  • Resilient: Always enough servers to handle load
  • Efficient: You don’t overpay for unused capacity
  • Self-healing: Unhealthy EC2s get replaced automatically

💥 How It Works (Step-by-Step)

  1. Launch Template – This defines what EC2s to launch (AMI, instance type, scripts, etc)
  2. Auto Scaling Group (ASG) – This defines how many EC2s to run, in which subnets/AZs
  3. Scaling Policy – This defines when to scale (like if average CPU > 60%)

🔥 Target Tracking is the easiest policy — just tell AWS:
“Keep CPU around 60%” and it handles the rest!

🧠 Health Checks Are the Secret Sauce

The load balancer only routes traffic to healthy instances. You define:

  • Simple TCP checks (is the port open?)
  • Or HTTP checks like /health or /monitor (is the app actually running?)

Once a new EC2 passes its health check, it starts receiving real traffic.

🧪 Real-World Demo: Auto Scaling in Action

Imagine you simulate load on your app (like a "Stress CPU" button):

  • CPU usage spikes ⬆️
  • CloudWatch triggers an alarm 🚨
  • Auto Scaling launches new EC2s 💻💻
  • ELB starts routing traffic to them 🧭
  • CPU load drops ⬇️

And when demand falls again? The group automatically scales back down.

🔁 Horizontal vs Vertical Scaling

Scaling Type What It Does Auto Scaling?
Vertical Make one EC2 bigger ❌ Manual
Horizontal Add more EC2s ✅ Fully automated

With stateless apps, horizontal scaling wins every time. No need to rewrite the app — just spin up more servers.

🎯 When Should You Use ELB + Auto Scaling?

✅ You have unpredictable or bursty traffic
✅ You want zero manual intervention
✅ You care about high availability and cost-efficiency
✅ You want to build a resilient, cloud-native architecture

🧩 Final Thoughts

You don’t need to be a DevOps pro to start using load balancing and auto scaling. With just a launch template, a target tracking policy, and a couple of healthy EC2s, you’re already halfway there.

☁️ The cloud is about working smarter, not harder.
If your app can scale with demand, you can sleep at night knowing AWS is doing the heavy lifting.

If you’ve tried this setup or have questions about how to make it work in your project, I’d love to connect! Drop a comment or hit me up on LinkedIn 💬

Keep building cool stuff in the cloud 💻🚀

Top comments (0)