Working with ECS

22.08.2018, last updated 05.03.2021 - Jeremy T. Bouse

By this point we should have a VPC in place and our Private tier subnets can route out either a NAT Gateway or VPN Connection that performs NAT, we can then begin to look at deploying applications into the environment in earnest. In my environment I’ve made the choice to use containers as much as possible so the most logical next step is to setup an Elastic Container Service (ECS) cluster.

Setting up your Virtual Private Cloud

21.08.2018, last updated 05.03.2021 - Jeremy T. Bouse

If you’ve already followed along from my earlier posts on getting started with AWS and my update to getting started, then by now you should have a multi-tiered VPC across multiple Availability Zones which is setup along the lines that the diagram below displays. Your VPC will have a single Internet Gateway and 2 Gateway Endpoints going to S3 and DynamoDB. Each of the subnets will also have their own Route Table which establishes the routes available from within the subnet.

Getting started with Amazon Web Services

13.08.2018, last updated 05.03.2021 - Jeremy T. Bouse

When starting to operate in Amazon Web Services (AWS) you have to decide whether to utilize the Default Virtual Private Cloud (VPC) or define your own VPC. The Default VPC typically sets itself up using the 172.31.0.0/16 CIDR block and a single tier of available subnets in all Availability Zones (AZ) with the region. This is fine for general use but to setup a proper tiered security model you’ll want to define your own VPC.