

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
click for more info
Not enough gems
Cost: 6 gems
1: VPC and Networking Setup
incomplete
2: Why ECS?
incomplete
3: Elastic Container Registry
incomplete
4: ECR Repo
incomplete
5: ECS Clusters
incomplete
6: ECS Permissions
incomplete
7: ECS Task Definitions
incomplete
8: ECS Security Groups
incomplete
9: Application Load Balancer
incomplete
10: Target Groups
incomplete
11: CloudWatch Log Groups
incomplete
12: ECS Services
incomplete
13: Cleanup
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
I know that it looks like we're working on anything but ECS and containers at the moment, but I promise we're getting closer. We just have to shave a few more yaks.
Now it's time to start listening for traffic. To do that, we'll set up a Load Balancer and a Listener.
A load balancer sits in front of our service and distributes incoming traffic across your task(s). It handles things like health checks, SSL termination, and routing traffic to healthy containers. We'll place the load balancer in public subnets so it can receive traffic from the internet.
To make this work, we need several pieces:
Create an Application Load Balancer named patientping-alb with a listener that returns a static response.
Cost check: This is the part that will cost money. An ALB costs about $0.0225 per hour (~$16/mo) plus data transfer costs. This is an important part to tear down when we tell you to.
200text/plainLoad balancer is working!Run and submit the tests to verify your load balancer is configured correctly.