ECS Infrastructure
Templates Needed
There are two templates that are to be deployed as part of this:
- ecs-clusters.yml
- load-balancers.yml
ECS Clusters These clusters are made per-account, and contain AutoScaling groups with launch configurations that automatically register each new instance with ECS. This ensures that our cluster creation is idempotent and repeatable, and allows us to treat our infrastructure as ephemeral.
The parameters for this are:
- EnvironmentName - where we deploy our ECS Clusters. This dictates VPCs, subnets, etc.
- InstanceType - Depending on what kind of cluster we want this to be, we can set much larger EC2s that are designed to be catered for compute (C4), memory (m4), or cheap (t2)
- ClusterSize - This is the minimum number of EC2s we will run as part of our cluster. This allows for redundancy and HA of our applications running in a cluster.
Load Balancers With this current implementation, we will have one load balancer per cluster. Each application being setup via it's own cloudformation template will register a new Target Group with this load balancer, allowing for cheaper load balancing (which can usually get very expensive).
The load balancer has the following parameters:
- EnvironmentName - Where this load balancer is deployed.
- LoadBalancerType - This can be a public or private load balancer, which provisions it in different subnets on our current VPC setup. Private load balancers are for communications between applications within the same VPC. Public is for internet-facing load balancers.