Serverless Containers: Deploying Application On ECS and Fargate

Welcome to my workshop on Amazon Elastic Container Service(Amazon ECS) and AWS Fargate!

In this workshop, we will dive into the core concepts of Amazon ECS and AWS Fargate, exploring what they are and how they work. We will also apply our acquired knowledge by deploying a to-do application called Momentum on these services. Then, we will construct a CI/CD pipeline for our application utilizing AWS developer tools, such as AWS CodePipeline, AWS CodeBuild.

Target Audience

This workshop is designed for beginners who are new to AWS and want to learn about Amazon ECS and AWS Fargate.

Prerequisites

You should have a basic understanding of AWS networking, as well as the fundamentals of Docker and containers. If you don’t, no worries-I recommend you to take the following workshops first:

• Amazon VPC and AWS Site-to-Site VPN Workshop

• What is a Container?

Time

This workshop might take up to 3 hours to complete.

Workshop Modules

1. Introduction: Introduce the to-do application, Momentum, that we will deploy. We will review the cloud architecture and examine the fundamentals of Amazon ECS and AWS Fargate.

2. Networking Configuration: Set up the foundational AWS networking infrastructure including VPC, subnets, internet gateway, NAT gateway, route tables, and security groups.

3. Cluster Setup: Create and configure the Amazon ECS cluster, set up secrets management, deploy the core and admin applications, and enable service-to-service communication.

4. Debugging With ECS Exec: Configure ECS Exec functionality to enable secure shell access to running containers for debugging and troubleshooting.

5. Configure the Standard CI/CD Pipeline: Build a continuous integration and deployment pipeline using AWS CodePipeline and CodeBuild to automate application deployments.

6. Configure Service Auto Scaling: Implement automatic scaling policies to handle varying application loads efficiently.

7. Cleanup: Clean up all AWS resources created during the workshop to avoid ongoing costs.

Overall Architecture - Application & Networking Flow

Overall Architecture - Developer Flow