In a prior video ( • Containers with Amazon... ), I introduced you to the basics of working with the Elastic Container Service (ECS) on AWS. But in that video, we only used a single container, accessing it from the container’s public IP address.
In this video, we’ll make things more real-world, by running multiple containers and balancing traffic across them using an Application Load Balancer (ALB).
In a hands-on tutorial, we’ll create two security groups-one for the ALB and one for the ECS service. Then we’ll create an ECS cluster and task definition that pulls in an NGINX container from the Amazon Elastic Container Registry (ECR) Public Gallery. From there, we’ll create the ECS service, and while doing that, we’ll create the Application Load Balancer. But there’s a gotcha here! Make sure you stay to the end to find out how to get the load balancing working properly.
🌟🌟If you’re interested in getting AWS certifications, check out these full courses. They include lots of hands-on demos, quizzes and full practice exams. Use FRIENDS10 for a 10% discount!
- AWS Certified Cloud Practitioner: academy.zerotomastery.io/a/af...
- AWS Certified Solutions Architect Associate: academy.zerotomastery.io/a/af...
00:00 - Overviewing what we’ll be building, and the need for a load balancer with ECS
01:38 - Understanding the security groups we need to get the load balancer working in ECS
02:43 - Creating two security groups in the AWS Console
04:43 - Creating an ECS Cluster
05:38 - Creating a new task definition for NGINX
07:12 - Deploying the ECS service
08:30 - Creating the load balancer to work with the ECS service (warning: There’s a gotcha here!)
10:08 - Testing our load balancer
10:34 - The load balancer doesn’t work!
10:58 - Fixing the security groups so that our load balancer works
12:00 - Now the load balancer works with our ECS containers!
12:22 - Summarizing what we’ve built
12:33 - IMPORTANT!! Deleting your ECS task, service, cluster, task definition, load balancer and security groups
20 июл 2024
