Overview of containers and AWS ECS, including reference to the new Fargate option.

1. Containers and ECS Overview
Prepared by: Stenio Ferreira, Solution Architect
Contact: stenio.ferreira@slalom.com
Date: 12/18/2017

2. Agenda
• Containers
– Definition
– Containers vs. VMs
– Benefits/risks
• Docker
– Overview
– Workflow
– Example CI/CD Pipeline
• ECS/ ECR
– Overview
– Reference architecture
• Fargate

3. Containers: Definition
A container image is a lightweight, stand-alone,
executable package of a piece of software that includes
everything needed to run it: code, runtime, system tools,
system libraries, settings.
Available for both Linux and Windows based apps,
containerized software will always run the same,
regardless of the environment.
Containers isolate software from its surroundings, for
example differences between development and staging
environments and help reduce conflicts between teams
running different software on the same infrastructure.

4. Containers vs. VMs

5. Containers: Benefits/ Risks
Benefits
• Consistency across environments
• Version control
• Serves as documentation of what is
Deployed
• Flexibility of base image (OS type,
installed languages and apps)
• Faster to start than a VM
Risks
• Increased complexity on areas
such as networking and logging
• Ephemeral nature might
require paradigm shift
• Security risks associated with
public base images
• Developers need to learn new
workflow

6. Docker: Overview

7. Docker: Workflow

8. Docker: Example CI/CD
Source: https://ssokurenko.github.io/docker-intro

9. ECS: Overview

10. ECS: Reference Architecture
https://github.com/awslabs/ecs-refarch-cloudformation

11. ECS: Fargate