Elastic Container Service - Lexicon

The Lexicon is an open source project available on GitHub, the steps below setup the infrastructure in AWS using the AWS Console. There is a stack overview here that shows how the infrastructure works together. Alternatively this can also be done from the CLI.

Cluster

Login to the Console and search for ECS and select create new cluster.

Instance configuration

1
Type:                            EC2 Linux + Networking

This will also create the following resources:

  • Cluster
  • VPC
  • Subnets
  • Auto Scaling group with Linux AMI
1
2
Cluster name:                    lexicon-cluster
Provisioning Model: On-Demand Instance

With On-Demand Instances, you pay for compute capacity by the hour, with no long-term commitments or upfront payments.

1
2
3
4
5
EC2 instance type:               m5.large
Instances: 1
EC2 Ami Id: *select if setup
EBS storage (GiB): 22
Key pair: *select if setup on EC2

Networking

Configure the VPC for your container instances to use. A VPC is an isolated portion of the AWS cloud populated by AWS objects, such as Amazon EC2 instances. You can choose an existing VPC, or create a new one with this wizard.

1
2
3
4
5
6
VPC:                             create new
CIDR block: 10.0.0.0/16
Subnet 1: 10.0.0.0/24
Subnet 2: 10.0.1.0/24
Security group: create new
Security group inbound rules: 0.0.0.0/0:80

Container instance IAM role

The Amazon ECS container agent makes calls to the Amazon ECS API actions on your behalf, so container instances that run the agent require the ecsInstanceRole IAM policy and role for the service to know that the agent belongs to you. If you do not have the ecsInstanceRole already, we can create one for you.

1
Container instance IAM role:     ecsInstanceRole

Tags

These are key value

1
Description:lexicon

CloudWatch Container Insights

CloudWatch Container Insights is a monitoring and troubleshooting solution for containerized applications and microservices. It collects, aggregates, and summarizes compute utilization such as CPU, memory, disk, and network; and diagnostic information such as container restart failures to help you isolate issues with your clusters and resolve them quickly.

1
CloudWatch Container Insights:    [X] Enable Container Insights

Clicking create will then create all of the following resources

  • ECS cluster - ECS Cluster lexicon-cluster successfully created
  • ECS Instance IAM Policy - IAM Policy for the role ecsInstanceRole successfully attached
  • CloudFormation Stack - CloudFormation stack EC2ContainerService-lexicon-cluster and its resources successfully created

Cluster resources

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Instance typem5.large
Desired number of instances1
Key pair
ECS AMI IDami-0c7dea114481e059d
VPCvpc-0f7c247aaee86898a
Subnet 1subnet-034b4e1648e087e00
Subnet 1 route table associationrtbassoc-0f00a646e08954693
Subnet 2subnet-035ef093933b3004d
Subnet 2 route table associationrtbassoc-06baa9d9966bdc321
VPC Availability Zonesap-southeast-2a, ap-southeast-2b, ap-southeast-2c
Security groupsg-0bf09a7725e98639a
Internet gatewayigw-059a6dde43c07265b
Route tablertb-0f5117a414443aa77
Amazon EC2 routeEC2Co-Publi-1CGPQELKTIYXG
Virtual private gateway attachmentEC2Co-Attac-160S89W6RPC2V
Launch configurationEC2ContainerService-lexicon-cluster-EcsInstanceLc-1FBGSYZZTIHOC
Auto Scaling groupEC2ContainerService-lexicon-cluster-EcsInstanceAsg-1UZUKKM0HD2K6

Task Definitions

From Task Definitions select Create new Task Definition

1
2
3
4
5
Launch type: EC2 
Task Definition Name: lexicon-definition
Requires Compatibilities: EC2
Task Role: ecsTaskExecutionRole
Network Mode: Bridge (FARGATE will only have awsvpc)

Task execution IAM role

This role is required by tasks to pull container images and publish container logs to Amazon CloudWatch on your behalf. If you do not have the ecsTaskExecutionRole already, we can create one for you.

1
Task execution role:              ecsTaskExecutionRole

Task size

The task size allows you to specify a fixed size for your task. Task size is required for tasks using the Fargate launch type and is optional for the EC2 launch type. Container level memory settings are optional when task size is set. Task size is not supported for Windows containers.

1
Task memory (GB):                 4096

The amount of memory (in MiB) used by the task. It can be expressed as an integer using MiB, for example 1024, or as a string using GB, for example ‘1GB’ or ‘1 gb’.

1
Task CPU (vCPU):                  2048   (512 = 0.5 vCPU, 1024 = 1 vCPU, 2048 = 2 vCPU)

The number of CPU units used by the task. It can be expressed as an integer using CPU units, for example 1024, or as a string using vCPUs, for example ‘1 vCPU’ or ‘1 vcpu’.

Add Container (WEB)

This is the ASP.NET MVC web application.

Standard
1
2
3
4
Container name:          lexicon-web
Image: 000000000000.dkr.ecr.ap-southeast-2.amazonaws.com/lexicon-test
Memory Limits (MiB): soft 512
Port mappings: 0 -> 80

Port mappings: 0 means any from the host

Advanced container configuration
1
2
Essential:               un-check 
Log configuration: [x] Auto-configure CloudWatch Logs

Essential, if you check this and your process exits, then the entire task is shut down as well. At least one of your containers HAS to have this checked.

Add Container (SQL)

1
2
3
4
Container name:          lexicon-sql
Image: microsoft/mssql-server-linux:2017-CU13
Memory Limits (MiB): soft 2048
Port mappings: 0 -> 1433
1
2
Environment variables:   LEXICON_SQL_CONNECTION|Password123
ACCEPT_EULA|Y

You may also designate AWS Systems Manager Parameter Store keys or ARNs using the ‘valueFrom’ field. ECS will inject the value into containers at run-time.

1
2
Essential:               check
Log configuration: [x] Auto-configure CloudWatch Logs

Task (run once off)

  • Clusters -> lexicon-cluster -> tasks -> run new task
1
2
3
4
Launch type:             EC2
Task Definition: lexicon-definition:1
Cluster: lexicon-cluster
Number of tasks: 1

Then hit Run Task and wait for the status to change to RUNNING

  • Clusters -> select task -> expand container
    Click external link

Service

Start from task definition and keep it running as apposed to running the task as once off.

References