AWS Applications Deployment Basics – Part 1 (VPC and PostgreSQL Setup)

Introduction

In this series about deploying applications in AWS, I will discuss different methods and steps required to run different applications in AWS. We will be covering different moving parts in AWS as needed to run typical applications.

This series will be arranged in different parts to discuss different services, topics and/or technologies needed for application deployment and execution.

Databases are one of the basic building block of many different type of applications. They can be relational or NoSQL or both. In this post, we will cover how to setup a PostgreSQL database running on AWS EC2 in a private-subnet of a VPC.

Then we will try to connect to it via a NodeJS application which will be running locally on the same machine.

Background

I’ve recently written some posts about different Amazon Web Services. In those posts I covered many different areas of AWS and those shall provide enough background information to help us deploy various application workloads in AWS.

Here are the Links:

• A High-Level Introduction to AWS
• How to Create an AWS Relational Database Service (RDS)
• Amazon VPC Basics
• An Introduction to AWS Internet Gateway and VPC Routing
• An Introduction to AWS EC2 (Elastic Compute Cloud)
• AWS Basics – Bastian Hosts and NATS
• A Beginner’s Guide to AWS Security Groups

If you are new to AWS or want to refresh some of the background knowledge which I will be using in this series, you can read the above mentioned posts as needed.

I have already setup a VPC with public and private subnets, created internet gateway, security groups and route tables and configured the traffic flow.

VPC Setup

Here is how the VPC is setup. It has two subnets, an internet gateway, two custom route-tables and few security groups:

Subnets

• fm-pub-subnet (Public subnet)
• fm-private-subnet (Private Subnet)

Security Groups:

• Lambda-sg
• nat-server-sg
• fm-private-sg

I also configured inbound/outbound rules as shown in the diagram above.

Next, I launched two EC2 instances (one in each subnet) as shown in diagram below:

Instance 1:

• Amazon Linux Image setup as a NAT Server
• nat-server-sg Security-Group attached

Instance 2

• Ubuntu Image (this also has git tools)
• fm-private-ubuntu-sg Security-Group attached
• lambda-sg Security-Group attached (we will use it later)

Starting Point

AWS Infrastructure setup up to this will be the starting point for this series. You can learn about all above parts needed to setup this infrastructure from the posts links mentioned above.

Installing PostgreSQL on Ubuntu EC2

Now, we want to install postgreSQL on ubuntu EC2 instance running in private subnet.

1. Make an SSH Jump

ssh -i fm-keypair.pem ec2-user@elastic-ip-bastianserver //ssh to bastian
ssh -i ./fm-keypair.pem ubuntu@10.0.2.99 //ssh to private ubuntu EC2

2. Update Packages on Ubuntu

sudo apt-get update

3. Install Postgres on Ubuntu

sudo apt-get -y install postgresql

4. Test Installation using PSQL

Cool. installation is done and lets do a small test to confirm that it is working.

sudo -i -u postgres
psql
\l

here is the output of actions:

5. Create Database

Let’s create a database using SQL:

CREATE DATABASE productsdb;

Next, connect to productsdb and create a products table by executing some SQL:

\c productsdb

CREATE TABLE products (
    id serial NOT NULL PRIMARY KEY,
    name varchar(255) NOT NULL,
    serialno varchar(255),
    createdat TIMESTAMPTZ DEFAULT NOW()
);

SELECT * from products;

and you can see that table is created as expected:

Next, Let’s insert some test data using SQL as follows:

INSERT INTO products( name, serialno)
VALUES
( 'Product A', 'A12345678'),
( 'Product B', 'B12345678'),
( 'Product C', 'C12345678'),
( 'Product D', 'D12345678'),
( 'Product E', 'E12345678')

and if we execute select statement again, we can see that now we have some test data in the table:

Ok, upto this point, the postgres installation is working as expected, we also created a database with one products table and some test data.

Also, you can change the password for postgres as follows:

sudo -u postgres psql -c "ALTER USER postgres WITH PASSWORD 'sasa';"

So far, we are executing SQL statements locally on the EC2 instance which we are connected to via Bastian Host (aka jump-server).

Now, instead of PostgreSQL, if you wat to use MySQL, you just need to execute the corresponding apt-get commands to install relevant package on ubuntu machine.

Having a database in private subnet is a good practice. It is secure that there is no direct incoming internet traffic to private subnet and we have control over who has access.

Connecting with an application running locally

This part is optional, you can use Java, .NET Core, Python or any other programming language. I’ve created a very simple git repo for a Nodejs application. The application tries to read data from productsdb database and products table. I cloned the repository on the same ubuntu instance where postgres is installed:

>>git clone https://github.com/jawadhasan/nodepostgresdemo.git
>>cd nodepostgresdemo
>>npm install

Then simply run the application:

You can see that server is up and running.

If for some reason node or npm is not installed on your ubuntu machine, you can install those using following commands:

node -v
npm -v


sudo apt install nodejs
sudo apt install npm

Test the Local Application

Now, I make another SSH connection to ubuntu EC2 (via jump host) and make a curl request on port 3000 as follows:

and as you can see the Node application is able to read the data from postgres database.

Here is code for server.js:

Node application is simply using pg library for the database connection and query and returning the data.

Following diagram shows application and database running on same EC2 instance:

Summary

This was the first post in series about application deployments on AWS. We talked about some background information and discussed a basic VPC setup with two subnets and two EC2 instances.

We then installed PostgreSQL on an ubuntu EC2 instance running in a private subnet with some test data. We also test the database connectivity with a locally running Nodejs application. You can download the application code from this git repo.

Later, we will be running our application on a different EC2 instance and then will check if our application can access the database while running on different EC2 or not, and what can be needed to make that happen. Let me know if you have some comments or questions. Till next time, Happy coding.

My Recent Books