AWS ECS Fargate Container Deployment
Deployed a containerized web application on Amazon ECS using AWS Fargate, Amazon ECR, an Application Load Balancer, and managed AWS networking.
// ARCHITECTURE_TOPOLOGY
Problem Statement & Context
Deploy a containerized web application on AWS using a managed compute model that removes the need to provision or maintain EC2 instances while providing reliable traffic routing and container service management.
Solution & Delivery Approach
Built and tagged a Docker container image, pushed it to Amazon ECR, and created an Amazon ECS task definition and service using AWS Fargate. Integrated the service with an Application Load Balancer and target group, configured the required VPC networking and security groups, and validated application access through the load balancer endpoint.
Engineering Challenges & Resolution
ECS service creation initially failed because the required ECS service-linked role was unavailable. Resolved the IAM dependency, completed the service creation, and verified that the Fargate task registered successfully with the Application Load Balancer target group.
// Key_OUTCOMES
- ✓Successfully deployed and exposed a containerized web application using Amazon ECS and AWS Fargate without managing EC2 instances.
- ✓Established an end-to-end deployment flow from a local Docker image to Amazon ECR and running Fargate tasks.
- ✓Configured load-balanced access and health-based target registration through an Application Load Balancer.
- ✓Gained practical experience integrating ECS, Fargate, ECR, Elastic Load Balancing, IAM, and VPC networking.
// RESPONSIBILITIES
- >Built and tagged a Docker image and published it to a private Amazon ECR repository.
- >Created an Amazon ECS cluster, Fargate task definition, and ECS service with the required CPU, memory, container port, and execution-role configuration.
- >Configured VPC networking, subnets, and security groups for communication between the Application Load Balancer and Fargate tasks.
- >Created an Application Load Balancer, listener, and target group with application health checks.
- >Diagnosed and resolved the ECS service-linked IAM role issue that initially prevented service creation.
- >Validated application availability through the load balancer endpoint and removed lab resources after testing to avoid unnecessary AWS charges.