A Guide to Deploy a Node.js Web App on AWS: Part 1

Introduction

Node.js is a well-known open-source server environment. It’s a platform built on Chrome’s JavaScript runtime environment for easily building fast and scalable network applications.

In this blog, we will deploy a high-availability Node.js Web App using AWS Elastic Beanstalk and Amazon DynamoDB. We will be using a sample app that uses Node.js, Express, and a NoSQL database.

It automatically scales the app up and down on its specific need using easily adjustable Auto Scaling settings. For fast and flexible NoSQL database service, we will use Amazon DynamoDB, which provides consistent, single-digit millisecond latency at any scale. Amazon DynamoDB is a fully managed cloud database supporting document and key-value store models.

Architecture Diagram

Architecture Diagram to serve the Node.js app using AWS Elastic Beanstalk & DynamoDB

Step-by-Step Guide

• Create an AWS account: If you don’t have one already, create an AWS account at https://aws.amazon.com/ and log in.
• Set up AWS Elastic Beanstalk
  1. Open the Elastic Beanstalk console using the preconfigured link below:
     Elastic Beanstalk Console
  2. For Platform, we need to select the platform and the platform branch that matches the language used by the application.
  3. Then, we need to select the Application code and Sample application.
  4. Choose ‘Review and launch’.
  5. Review the options available, then choose the option you want to use and choose the ‘Create app’ when ready.

Elastic Beanstalk will take about five minutes to create the environment with the following resources:

• EC2 instance – An Amazon Elastic Compute Cloud (EC2) virtual machine configured to run web apps on our chosen platform.
• Instance Security Group – EC2 service group is configured to allow inbound traffic on port 80, which lets HTTP traffic from the load balancer reach the EC2 instance running in the web app. So, by default, traffic isn’t allowed on the other ports.
• Load Balancer – An Elastic Load Balancing load balancer is configured to distribute requests to the application instances. A load balancer also eliminates the need to expose the instance directly to the internet.
• Load Balancer security group – The load balancer security group is the same as the EC2 security group and does the same task. This resource lets the HTTP traffic from the internet reach the load balancer.
• Auto Scaling group – An Auto Scaling group is configured and made available to replace an instance if terminated or unavailable.
• Amazon S3 bucket – A storage location for the source code, logs, or other artifacts created when Elastic Beanstalk is used.
• Amazon CloudWatch alarms – Amazon CloudWatch alarms set Two alarms that are triggered if the load is too high or too low. When the alarm is triggered, the ‘Auto Scaling group’ scales up or down in response.
• AWS CloudFormation Stack – CloudFormation is used by Elastic Beanstalk to launch the resources in the environment and propagate configuration changes. These resources are defined in a template that can be viewed in the AWS CloudFormation console
• Domain Name – The domain name which will route the web app in the form subdomain.region.elasticbeanstalk.com.

Elastic Beanstalk manages all the resources, and when we terminate the environment, it terminates all of the resources it contains.

Note: The Amazon S3 bucket that Elastic Beanstalk creates is shared between environments, and it’s not deleted during the environment termination.

Conclusion

Elastic Beanstalk provisions, underlying infrastructure (e.g., Amazon EC2 instances), and management environment. Elastic Beanstalk benefits and provides many configuration options that make an easily manageable environment.

Check out the blog for Part -2 here.

About CloudThat