AWS CSA
  • Introduction
  • 1. AWS Overview
    • 1.1 AWS global Infrastructure
    • 1.2 Networking and Content Delivery
    • 1.3 Computing
    • 1.4 Storage
    • 1.5 Databases
    • 1.6 Migration Services
    • 1.7 Analytics
    • 1.8 Security and Identity
    • 1.9 Management Tools
    • 1.10 Application Services
    • 1.11 Developer Tools
    • 1.12 Mobile Services
    • 1.13 Desktop and App Streaming
    • 1.14 Artificial Intelligence
    • 1.15 Messaging
  • 2. IAM - Identity Access Management
    • 2.1 IAM Introduction
    • 2.2 IAM Labs
    • 2.3 Create a billing alart
    • 2.4 IAM Conclusion
  • 3. S3 - Simple Storage Service
    • 3.1 S3 Introduction
    • 3.2 S3 Labs
    • 3.3 Version Control Labs
    • 3.4 Cross Region Replication
    • 3.5 Life Cycle Management
    • 3.6 CloudFront
    • 3.7 CloudFront Labs
    • 3.8 S3 Security and Encryption
    • 3.9 Storage Gateway
    • 3.10 Snowball
    • 3.11 Snowball Labs
    • 3.12 S3 Transfer Acceleration
    • 3.13 Create a static web page using S3
    • 3.14 Storage Summary
  • 4. EC2 - Elastic Compute Cloud
    • 4.1 EC2 Introduction I
    • 4.2 EC2 Introduction II
    • 4.3 EC2 Lab 1
    • 4.4 EC2 Lab 2
    • 4.5 Security Groups Lab
    • 4.6 Upgrade EBS Volume Types - Lab1
    • 4.7 Upgrade EBS Volume Types - Lab2
    • 4.8 RAID, Volumes & Snapshots
    • 4.9 Create An AMI - Lab
    • 4.10 AMI's EBS Root Volumes vs. Instance Store
    • 4.11 Elastic Load Balancer & Health Check - Lab
    • 4.12 CloudWatch EC2 - Lab
    • 4.13 The AWS Command Line & EC2
    • 4.14 Using IAM Roles with EC2
    • 4.15 S3 CLI & Regions
    • 4.16 Using Bootstrap Scripts
    • 4.17 EC2 Instance Metadata
    • 4.18 Launch Configurations & Auto Scaling Groups
    • 4.19 EC2 Placement Groups - Exam Must Know
    • 4.20 Elastic File System (EFS) Lab
    • 4.21 Lambda Concepts
    • 4.22 Build A Serverless Webpage Using API Gateway & Lambda
    • 4.23 Use Polly to Pass Your Exam - Lab of a Serverless Application
    • 4.24 Use Polly to Pass Your Exam - Lab of a Serverless Application
    • 4.25 EC2 - Summary & Exam Tips
  • 5. Route53
    • 5.1 DNS 101
    • 5.2 Route53 - Register A Domain Name - Lab
    • 5.3 Setup Our EC2 Instances - Lab
    • 5.4 Routing Policies - Lab
  • 6. Databases on AWS
    • 6.1 Databases 101
    • 6.2 Launching an RDS Instance - Lab
    • 6.3 RDS - Backups, Multi-AZ & Read Replicas
    • 6.4 DynamoDB
    • 6.5 Redshift
    • 6.6 ElastiCache
    • 6.7 Aurora
    • 6.8 Database Summary
  • 7. VPC
    • 7.1 VPC Overview
    • 7.2 VPC Lab - Part 1
    • 7.3 VPC Lab - Part 2
    • 7.4 NAT Instances & NAT Gateways
    • 7.5 Network Access Control Lists vs. Security Groups
    • 7.6 Load Balancers & Custom VPCs
    • 7.7 VPC Flow Logs
    • 7.8 NATs vs. Bastions
    • 7.9 VPC End Points
    • 7.10 VPC Clean Up
    • 7.11 VPC Summary
  • 8. Application Services
    • 8.1 SQS - Simple Queue Service
    • 8.2 SWF - Simple Workflow Service
    • 8.3 SNS - Simple Notification Service
    • 8.4 Elastic Transcoder
    • 8.5 API Gateway
    • 8.6 Kinesis 101
    • 8.7 Kinesis Streams Lab
    • 8.8 Application Services Summary
  • 9. White Paper Reviews
    • 9.1 Overview of AWS
    • 9.2 Overview of Security Processes - Part 1
    • 9.3 Overview of Security Processes - Part 2
    • 9.4 Risk & Compliance Whitepaper
    • 9.5 Storage Options in the Cloud Whitepaper
    • 9.6 Architecting For The Cloud Best Practices Whitepaper
  • 10. Well Architected Framework
    • 10.1 Introduction of Well Architected Framework
    • 10.2 Pillar One - Security
    • 10.3 Pillar Two - Reliability
    • 10.4 Pillar Three - Performance
    • 10.5 Pillar Four - Cost Optimization
    • 10.6 Pillar Five - Operational Excellence
    • 10.7 Well Architected Framework - Summary
  • 11. Additional Exam Tips
    • 11.1 Exam Tips Based On Student Feedback
    • 11.2 Consolidated Billing
    • 11.3 AWS Organizations - Lab
    • 11.4 Cross Accounts Access
    • 11.5 Resource Groups & Tagging
    • 11.6 VPC Peering & ClassicLink
    • 11.7 Direct Connect
    • 11.8 Security Token Service
    • 11.9 Active Directory Integration
    • 11.10 Workspaces
    • 11.11 ECS - Part 1 - What is Docker
    • 11.12 ECS - Part 2 - What is ECS
    • 11.13 CloudFormation - A Brief Introduction
    • 11.14 Step Functions - A Brief Introduction
  • 12. Practice Tests Questions Summary
    • 12.1 Whizlabs - Free Test
    • 12.2 Whizlabs - Diagnosis Test
    • 12.3 Whizlabs - Practice Test I
    • 12.4 Whizlabs - Practice Test II
    • 12.5 Whizlabs - Practice Test III
    • 12.6 Whizlabs - Practice Test IV
    • 12.7 Whizlabs - Practice Test V
    • 12.8 Whizlabs - Practice Test VI
    • 12.9 Whizlabs - Practice Test VII
    • 12.10 Whizlabs - Section Tests - Part 1
    • 12.11 Whizlabs - Section Tests - Part 2
    • 12.12 Udemy - Final Quiz
  • 13. The Real World - Creating a fault tolerant Word Press Site
    • 13.1 Getting Setup
Powered by GitBook
On this page
  • What is ECS
  • What is ECR
  • ECS Task Definitions
  • ECS Services
  • ECS Clusters
  • ECS Scheduling
  • ECS Container Agent
  • ECS Security
  • ECS Limits

Was this helpful?

  1. 11. Additional Exam Tips

11.12 ECS - Part 2 - What is ECS

What is ECS

  • ECS - Amazon's managed EC2 container service. Allows you to manage Docker containers on a cluster of EC2 instances.

  • ECS is a Regional service that you can use in one or more AZs across a new or existing, VPC to schedule the placement of containers across your cluster based on your resource needs, isolation policies, and availability requirements.

  • Amazon ECS eliminates the need for you to operate your own cluster management and configuration management systems, or to worry about scaling your management infrastructure.

  • ECS can also be used to create a consistent deployment and build experience, manage and scale batch and ETL workloads (Extract, Transform, Load. These are basically three different types of database functions. ETL workload pulls data from one database and converts it into a form that can be loaded into another database), and build sophisticated application architectures on a micro-services model (different functions of your application wrapped up in different docker containers).

  • Port mappings allow containers to access ports on the host container instance to send or receive traffic. Port mappings are specified as part of the container definition.

What is ECR

  • It is Amazon EC2 Container Registry. Amazon EC2 Container Registry (Amazon ECR) is a managed AWS Docker registry service. It is a managed AWS Docker registry service that is secure, scalable, and reliable. Amazon ECR supports private Docker repositories with resource-based permissions using AWS IAM so that specific users or Amazon EC2 instances can access repositories and images. Developers can use the Docker CLI to push, pull, and manage images.

ECS Task Definitions

  • A Task Definition is required to run Docker containers in Amazon ECS.

  • Task Definitions are text files in JSON format that describe one or more containers that form your application.

  • Think of a Task Definition as a CloudFormation Template but for Docker. Configure things such as the amount of CPU, RAM, etc.

  • Some of the parameters you can specify in a task definition include:

    • Which Docker images to use with the containers in your task.

    • How much CPU and memory to use with each container.

    • Whether containers are linked together in a task.

    • The Docker networking mode to use for the containers in your task.

    • What (if any) ports from the container are mapped to the host container instance.

    • Whether the task should continue to run if the container finished or fails.

    • The command the container should run when it is started.

    • What (if any) environment variables should be passed to the container when it starts.

    • Any data volumes that should be used with the containers in the task.

    • What (if any) IAM role your tasks should use for permissions.

ECS Services

  • An Amazon ECS Service allows you to run and maintain a specified number (or, the "desire count") of instances of a Task Definition simultaneously in an ECS cluster.

  • Think of Services like Auto-Scaling groups for ECS.

  • If a task should fail or stop, the Amazon ECS service scheduler launches another instance of your Task Definition to replace it and maintain the desired count of tasks in the service.

ECS Clusters

  • An Amazon ECS cluster is a logical grouping of container instances that you can place tasks on. When you first use the Amazon ECS service, a default cluster is created for you, but you can create multiple clusters in an account to keep your resources separate.

  • Concepts:

    • Clusters can contain multiple different container instance types.

    • Clusters are Region-specific.

    • Container instances can only be part of 1 cluster at a time.

    • You can create IAM policies for your clusters to allow or restrict users' access to specific clusters.

ECS Scheduling

  • Service Scheduler:

    • Ensure that the specified number of tasks are constantly running and reschedules tasks when a task fails. (For example, if the underlying container instance fails for some reason).

    • Can ensure tasks are registered against an ELB.

  • Customer Scheduler:

    • You can create your own schedulers that meet your business needs.

    • Leverage third-party schedulers, such as Blox.

  • The ECS Schedulers leverage the same cluster state information provided by the ECS API to make appropriate placement decisions.

ECS Container Agent

  • The Amazon ECS Container Agent allows container instances to connect to your cluster. The ECS Container Agent is included in the Amazon ECS-optimized AMI, but you can also install it on any EC2 instance that supports the Amazon ECS specification. The Amazon ECS Container Agent is only supported on EC2 instances.

  • When you need to connect your ECS Service to your registries hosted on DockerHub, you will need ECS Container Agent. The Amazon ECS container agent can authenticate with private registries, including Docker Hub, using basic authentication. When you enable private registry authentication, you can use private Docker images in your task definitions.

  • Pre-installed on special ECS AMIs.

  • Linux-based:

    • Work with Amazon Linux, Ubuntu, RedHat, CentOS, etc.

    • Will NOT work with windows.

ECS Security

  • You can use IAM with ECS to restrict access.

  • IAM Roles:

    • EC2 instances use an IAM role to access ECS.

    • ECS tasks use an IAM role to access services and resources.

  • Security Groups attach at the instance-level (i.e. the host level ... not the task or container level.)

  • You can access and configure the OS of the EC2 instances in your ECS cluster.

ECS Limits

  • Soft Limits:

    • Clusters per Region: default = 1000.

    • Instances per Cluster: default = 1000.

    • Services per Cluster: default = 500.

  • Hard Limits:

    • one-to-one mapping between ECS services and ELBs (Note: now we have dynamic host port mapping, so an ELB can be shared amongst multiple services using path-based routing)

    • 1000 Tasks per Service (the "desired count")

    • MAX 10 Containers per Task Definition

    • MAX 10 Tasks per instance (host)

Previous11.11 ECS - Part 1 - What is DockerNext11.13 CloudFormation - A Brief Introduction

Last updated 5 years ago

Was this helpful?