

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
As we dive into ECS (Elastic Container Service), I want to re-emphasize that having your networking set up correctly is critical. Luckily, we've already done it! Just know that it will be important that it's all still set up.
For ECS to work properly, we need:
10.0.0.0/22 (our patientping VPC)patientping-public-a and patientping-public-b)patientping-igw)0.0.0.0/0 to the Internet Gateway, associated with both public subnets (patientping-public-rt)We'll run our Fargate tasks and the load balancer in these public subnets. Tasks get outbound internet access (for example, to pull images from ECR) through the Internet Gateway, so we don't need a NAT Gateway for this course. (In production, you'd often use private subnets and a NAT Gateway or VPC endpoints for stronger isolation.)
Let's simply confirm that your VPC, subnets, Internet Gateway, and route table are still set up correctly.
If they're not, go back to to the "Network" chapter and make sure you have them setup correctly.
Run and submit the CLI tests to confirm your network setup.