In this post, I will guide you through the process of deploying a Node app on AWS ECS with Terraform.

Guide Overview

We will follow these steps:

1. Create a simple Node app and run it locally.
2. Dockerize the Node app.
3. Create an image repository on AWS ECR and push the image.
4. Create an AWS ECS cluster.
5. Create an AWS ECS task.
6. Create an AWS ECS service.
7. Create a load balancer.

The technologies used in this guide are:

• Amazon ECS — a fully managed container orchestration service
• Amazon ECR — a fully-managed Docker container registry
• Terraform — an open-source infrastructure as code tool

Prerequisites

• An AWS…

Today, I am going to show you how to build a highly available, secure and fault-tolerant application on AWS. We will be building this application together from first principles:

The components are as follows: (Don’t worry if you are not familiar with these terms, we will be going through this step-by-step):

• A VPC.
• Four subnets (two private and two public).
• An application load balancer.
• EC2 instances.
• An auto-scaling group that scales the instances horizontally.
• A PostgreSQL database replicated across to a different availability zone.

Infrastructure As Code

Infrastructure as code is a methodology of managing one’s infrastructure using configuration specifications.

In essence, rather than building one’s infrastructure with AWS’s UI, you can write a specification that defines the infrastructure you require. This specification is then provided to AWS CloudFormation which then spins up the underlying services for you. …

Introduction

A few weeks ago, I wrote a piece detailing how you can build a serverless API entirely through the AWS console UI:

In practise, you’d never actually build a production application this way, but it’s an excellent learning experience to do so.

Using infrastructure as code (IaC) is the proper way to build production serverless applications, and this piece will show you how to build the same application but much more elegantly and quickly with the AWS Serverless Application Model (AWS SAM).

Prerequisites

To follow this guide properly, you’ll need to go through the installation steps described in AWS’s own guide.

This involves signing up for an AWS account, installing the AWS CLI, installing the AWS SAM CLI, and creating an S3 bucket for your SAM applications. Note that you’ll need to use your bucket name throughout this guide, so remember it! …

Last week, I wrote five different articles about CI/CD services. In each article, I took this Node application and deployed it to AWS with a different CI/CD service. See the individual posts below:

Method

The steps followed for each CI/CD pipeline can be seen below. Notice how Docker Hub is used to store the built Docker images and Elastic Beanstalk is used to pull and run those images:

Introduction

This piece has two goals:

• To be a standalone guide to building a CI/CD pipeline with Travis
• To form part of a larger series of articles that compare various CI/CD services

The repository hosting the project tested and deployed with Travis can be found on GitHub. It’s a small Node/Express application that’s Dockerised and has a single test. I recommend you clone this application and push it up to your own GitHub account so you can build a pipeline while reading this guide.

Read my other CI/CD guides with this same application below:

The article comparing these services:

Pipeline Overview

A diagram showing the steps followed in our CI/CD pipeline can be seen below. Notice how we use Docker Hub to store our Docker images and Elastic Beanstalk to pull and run those…

Introduction

This piece has two goals:

• To be a standalone guide to building a CI/CD pipeline with Buddy
• To form part of a larger series of articles which compare various CI/CD services

The repository hosting the project tested and deployed with Buddy can be found here. It’s a small Node/Express application that’s Dockerised and has a single test. I recommend you clone this application and push it up to your own GitHub account so you can build a pipeline while reading this guide.

Read my other CI/CD guides with this same application below:

The article comparing these services:

Pipeline Overview

A diagram showing the steps followed in our CI/CD pipeline can be seen below. Notice how we use Docker Hub to store our Docker images and Elastic Beanstalk to pull and run those…

Introduction

This piece has two goals:

• To be a standalone guide to building a CI/CD pipeline with AWS CodePipeline
• To form part of a larger series of articles that compare various CI/CD services

The repository hosting the project tested and deployed with CodePipeline can be found on GitHub. It’s a small Node/Express application that’s Dockerised and has a single test. I recommend you clone this application and push it up to your own GitHub account so you can build a pipeline while reading this guide.

Read my other CI/CD guides with this same application below:

The article comparing these services:

Pipeline Overview

A diagram showing the steps followed in our CI/CD pipeline can be seen below. Notice how we use Docker Hub to store our Docker images and Elastic Beanstalk to pull and run those…

Introduction

This piece has two goals:

• To be a standalone guide to building a CI/CD pipeline with GitLab
• To form part of a larger series of articles which compare various CI/CD services

The repository hosting the project tested and deployed with GitLab can be found here. It’s a small Node/Express application that’s Dockerised and has a single test. I recommend you clone this application and push it up to your own GitHub account, so you can build a pipeline while reading this guide.

Read my other CI/CD guides with this same application below:

The article comparing these services:

Pipeline Overview

A diagram showing the steps followed in our CI/CD pipeline can be seen below. Notice how we use Docker Hub to store our Docker images and Elastic Beanstalk to pull and run those…