Cover image for Noob AWS: Why Amazon Web Services and Elastic Beanstalk Tutorial - Part 1

Noob AWS: Why Amazon Web Services and Elastic Beanstalk Tutorial - Part 1

th3n00bc0d3r profile image Muhammad ・5 min read

What is Amazon Web Services?

AWS (Amazon Web Services) is a collection of a set number of computers spread around the world. The set number of computers in a fixed area can be called a data center. The data center is connected through high speed internet that allows each data center to contribute its resource mainly space, ram and computing power to a single point that we call Amazon Web Services. This AWS further distributes these resources as per required capacity to its users who are you and me.

What was I doing before I discovered AWS?

I was managing servers. I was developing applications, deploying applications and then day/night managing servers. Its been 5 years, i have been going through the headache of managing it. I once remember a setup for one of my client, where I took 3 servers from different locations and using the WHM/Cpanel Cloud connecting them through IPs, was a real relief in knowing. I think it was 2-3 years back.

Why AWS Now?

I have been working on two of my projects, one that i deployed about 4 years back, it was never able to persist and not because of the deployment, it was the damn server, that always used to run out. It cost me a project, was a beautiful one, but a loss, so what do you do when things go like that, you follow a concept known as insanity. As someone said, "Insanity is the process of repeating something again and again and expecting a different result". Well I disagree to it, i think insanity is obsession, abyss to all the failures, one should never give up, so AWS has given me that new hope which i want to share.

3 Things to Know about AWS

  • EC2 - This is the Compute and RAM of your setup
  • S3 - This is the Hard drive or storage of your setup
  • Route53 - This is the Domain Management System
  • RDS - This is the Database of your System

What will AWS Do for me?

It will take the headache for me to stabilize the environment, it will give me a stable environment and all i need to do is work on my application. It will handle all the traffic issues as it will autoscale based on my traffic, it will charge me based on my usage and not fixate me to monthly retention.

What about alternatives to AWS?

Yes, there is google cloud and ali baba cloud but I think AWS has the market lead with have more than 1400+ services by start of 2019. Now these services are a mix and match of their basic service, providing usability based on a different use cases and it is likely you will fall in one.

What service I want to share, and what does it do?

Its called Elastic Beanstalk. EB is 1-2-3 deployment for my node projects. It also supports PHP, Ruby and .NEt. I just have to upload my code using a command line tool and amazingly after all the setup, its just one line and it handles the rest. It restarts my machine, gets my modules and makes sure it serves to my links aka APIs. In the meanwhile, I do have full control of the environment to make further tweaks.

Lets Start

Create a NOOB Node API Project

Create a Directory and Initialize a Package.json in it.

Lets install a couple of Modules we will be using

npm i -S express express mysql body-parser
  • ExpressJS - A framework we will use for our API Building Process
  • MySQL - A module driver to connect to MySQL
  • Body Parser - Help us send data to our API Post Calls

Next create an app.js file within the project.

const express       = require('express')
const bodyParser    = require('body-parser');
const app           = express()
const port          = 3000

app.get('/', (req, res) => {
    res.send("Welcome to the Noob API");

app.get('/test', (req, res) => {
    var response = {
        "success": true,
        "message": "Welcome to Mars"

app.listen(port, function() {
    console.log("Listening to " + port);

Now to run the project simple type

node app.js

It should start listening to port 3000, and now if you open the browser and type in http://localhost:3000/ you should have a simpler output


Lets get this over to AWS

First of all, we need the AWS Command Line tool and then we need the Elastic Beanstalk Command Line tool.

Installing AWS CLI
Now windows has an installer.

And for Linux and MacOS, you can refer to this, if you dont get it, let me know, i`ll help you with it. It uses PIP, its just a package manager.

Once installed, you can confirm as follows;

Installing EB CLI

Install Python

Remember to Check Add to Path


We should now have PIP in the Command Prompt, We install virtualenv, pyenv

pip install virtualenv

git clone https://github.com/pyenv/pyenv.git ~/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bash_profile
echo 'export PATH="$PYENV_ROOT/libexec:$PATH"' >> ~/.bash_profile
echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n eval "$(pyenv init -)"\nfi' >> ~/.bash_profile

Install CYGWIN and Install it in FULL

Now goto the aws-elastic-beanstalk-cli-setup/scripts/

python ebcli_installer.py

Now open Run from Windows and Paste this replacing your username

cmd.exe /c "C:\Users\<YOURUSERNAME>\.ebcli-virtual-env\executables\path_exporter.bat"


Then open terminal and type eb --version


You should now register an account with AWS. Then login to the following link

Welcome to the AWS Console and Dont Worry.

Type in IAM (Identity Access Management)

We need to create a user and connect it to our CLI, so we can access the AWS Cloud functions in our Command Line.

Click on User and Then Click on Add User

I am going to name my user win_cli and will only give it programmatic access. Click Next, lower bottom right of the screen

Next, Click on Attach Existing Policies Directory and Check Administrative Access. Then Click Next Tags

Tagging is a Good way, but i am not using it now, so leave it blank and click next, now you should have a review of you settings.

Click the Create User Button Now

Great, now copy your Access key ID and Secret access key . This is used to connect from the CLI to the Cloud of AWS. Now lets go back to the Command Prompt and type as follows;

Now to check it, type aws s3 ls in the command prompt and it shouldnt through any error.


Posted on by:

th3n00bc0d3r profile



By helping others, you learn how to help yourself. When the Noob is at work, remember it's not a Noob at work.


markdown guide