Overview

• Amazon ECS is a Container Management Service
• Services can be easily deployed, managed, and scaled
• AWS Fargate Launch Type—a serverless compute engine
• Elastic Compute Cloud (EC2) Launch Type to use managed EC2 instances in cluster
• AWS Fargate—run containers without having to manage servers or clusters of Amazon EC2 instances
• Configure CloudFormation Templates—define Launch Type, Server Definition, Auto Scaling Instructions, Security Groups, and Security Policies

Overall deployments

Legacy Deployments

• Need to self-manage instances
• Need intervention to scale the applications up or down
• Time-consuming

Amazon Web Services (AWS) Beanstalk

• User friendly
• Built-in health monitoring
• Scalability
• Unsuitable for complex applications

AWS Elasticsearch Kubernetes Service (EKS)

• Increased availability
• Not specific to platform
• Slightly costly compared to Amazon Elastic Container Service (ECS)
• High expectations to learn and adapt

Pros ECS’s greatest advantage is scalability

• It handles millions of requests per hour
• Applications can be scaled based on the system usage and load
• Need not worry about infrastructure when services are deployed
• There is integration with related AWS services
• Building the Continuous Integration & Continuous Delivery (CI/CD) pipeline helps build services, run tests, code analysis, and deployment
• Pricing Model helps in saving costs by paying only for the resources you use
• Save up to ~90% cost with Fargate & Fargate Spot Type

Cons

• User must understand concepts surrounding containerization, clusters, services, and ECS-specific tasks
• Using Spot Instance, AWS can recover any time making the application unstable at times