
#### Introduction

In this blog post we will quickly discuss the process to deploy our web apps to Amazon Elastic Compute Cloud. Amazon Elastic Compute Cloud is a part of Amazon.com's cloud-computing platform, Amazon Web Services, that allows users to rent virtual computers on which they run their own computer applications.

##### AWS Identity and Access Management (IAM)

AWS Identity and Access Management (IAM) provides fine-grained access control across all of AWS. With IAM, we can specify who can access which services and resources, and under which conditions. With IAM policies, we manage permissions to our workforce and systems to ensure least-privilege permissions.

IAM is an AWS service that is offered at no additional charge. To get started using IAM or if we have already registered with AWS, go to the [IAM console](https://console.aws.amazon.com/iam/home).

![AWS IAM](/images/AWS/IAM.webp)

##### Amazon EC2

Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers.

Amazon EC2’s simple web service interface allows us to obtain and configure capacity with minimal friction. It provides us with complete control of our computing resources and lets us run on Amazon’s proven computing environment. Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing us to quickly scale capacity, both up and down, as our computing requirements change.

![EC2 Instance](/images/AWS/EC2Instance.webp)

###### Steps To Launch Our Instance

- Choose an Amazon Machine Image (AMI)
  ![AMI](/images/AWS/UbuntuServer.webp)

- Choose Instance Type

  ![Instance Type](/images/AWS/InstanceType.webp)

- Configure Instance
- Add Storage
- Add Tags

- Configure Security Group
  ![Security Group](/images/AWS/SecurityGroup.webp)

- Review

  In the review phase make sure to preserve key pair, as it will be required to connect to the instance in the future.

  A key pair consists of a public key that AWS stores and a private key file that we store. Together they allow us to connect to our instance securely.
  ![Key Pair](/images/AWS/KeyPair.webp)

- Launch Status
  ![Launch Status](/images/AWS/LaunchInstance.webp)

Now we will connect to our instance.

![connect instance](/images/AWS/RunningInstance.webp)

![AWS Biling](https://relay.sh/static/4ad1b80f4baf091b838c6ad80fca1f5c/7016d/pay-your-aws-meme.jpg)

##### Access Our Instance

- Open an SSH Client
- Locate our private key file (access-key.pem).
- Our key must not be publicaly viewable for SSH to work. Use chmod 400 access-key.pem
- Connect to our instance using its Public DNS

Eg: ssh -i "access-key.pem" ubuntu@ec2-52-91-231-176.compute-1.amazonaws.com

We have successfully logged into our instance.

![Ubuntu Connected](/images/AWS/UbuntuConnected.webp)

##### Set up Node.js and git on our Linux instance

- Connect to your Linux instance as ec2-user using SSH.

- Install node version manager (nvm) by typing the following at the command line.
  ```console
  curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash
  ```
  ![AWS Node](/images/AWS/AWSNode.webp)
  We will use nvm to install Node.js because nvm can install multiple versions of Node.js and allow us to switch between them.
- Activate nvm by typing the following at the command line.
  ```console
  . ~/.nvm/nvm.sh
  ```
- Use nvm to install the latest version of Node.js by typing the following at the command line

  ```console
      nvm install node
  ```

  Installing Node.js also installs the Node Package Manager (npm) so we can install additional modules as needed.

- Test that Node.js is installed and running correctly by typing the following at the command line.

  ```console
      node -e "console.log('Running Node.js ' + process.version)"
  ```

- Now install git (our ubuntu instance will have git by default so we can simply do git --version to check)

###### Running our projects in EC2

- clone repo using
  ```console
      git clone "path" "folder name"
  ```
- install PM2 ,PM2 is a process manager which make sure that our node server is continuously running

  ```console
      npm i pm2 -g
  ```

  ![PM2 Install](/images/AWS/PM2.webp)

- go into project folder and run npm install

  ```console
      cd client
      npm install
      npm run build
  ```

- use PM2 for starting our server
  ```console
      pm2 start npm -- start
  ```
  ![NPM Start](/images/AWS/NPMStart.webp)

Now connect to our instance using its Public DNS

![Public DNS](/images/AWS/EC2Project.webp)

Here is our deployed site , but as we now see here that we have to append port to it to get it working.

##### NGINX

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Now we will install Nginx into our instance with following steps :

- sudo apt install nginx
  ![Install Nginx](/images/AWS/Nginx.webp)

- Now when we go to public DNS we will see the following , now we are ready to configure our Nginx Sever
  ![Ngnix Installed](/images/AWS/NginxInstalled.webp)

- navigate to sites-enabled

  ```console
  cd /etc/nginx
  ls
  cd sites-enabled
  ```

- update default with --- sudo vim default
  ![Nginx default](/images/AWS/nginx-default.webp)
- edit location
  ![Nginx location](/images/AWS/location-nginx.webp)

- Restart the server with -- sudo service nginx restart
  ![Restart Server](/images/AWS/nginx-restart.webp)

Here is our deployed web application

![Web App](/images/AWS/Nginx-location.webp)
