Book Image

Amazon Fargate Quick Start Guide

By : Deepak Vohra
Book Image

Amazon Fargate Quick Start Guide

By: Deepak Vohra

Overview of this book

Amazon Fargate is new launch type for the Amazon Elastic Container Service (ECS). ECS is an AWS service for Docker container orchestration. Docker is the de facto containerization framework and has revolutionized packaging and deployment of software. The introduction of Fargate has made the ECS platform serverless. The book takes you through how Amazon Fargate runs ECS services composed of tasks and Docker containers and exposes the containers to the user. Fargate has simplified the ECS platform. We will learn how Fargate creates an Elastic Network Interface (ENI) for each task and how auto scaling can be enabled for ECS tasks. You will also learn about using an IAM policy to download Docker images and send logs to CloudWatch. Finally, by the end of this book, you will have learned about how to use ECS CLI to create an ECS cluster and deploy tasks with Docker Compose.
Table of Contents (14 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Benefits of Fargate


The benefits in ECS are as follows:

  • A managed service for containerized applications that does not require much user input to run Docker applications
  •  Microservices consisting of multiple applications run in isolated containers
  •  Auto scales tasks based on application load
  •  Integrates with other AWS services including IAM, CloudWatch Logs, Elastic Load Balancing, CloudFormation templates, EBS Volumes, Batch, ECR, and CloudTrail logs
  •  A virtual private cloud (VPC) with no resources shared with other users
  •  Provides support for running a CodePipeline with ECS as the deployment platform
  • Supports the latest Docker version 17.0

Fargate provides the following additional benefits:

  • With a Fargate launch type, a user does not create or manage any EC2 instances, as none are exposed on the cluster.
  • Tasks are directly exposed to the user via an ENI.
  • The underlying infrastructure is provisioned by Fargate. EC2 instances are not to be managed with the Fargate launch type.
  • CodePipeline supports Fargate as a deployment platform.
  • Microservices based on Container definitions encapsulated in a task definition are explicitly linked, and are not to be linked with any additional options, such as links.
  • CloudWatch Logs may be auto configured.