Skip to content

Latest commit

 

History

History

02. Hosting Full-stack MERN application

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

Screenshots (WAIT FOR LOADING 6-7 GIF files) -

ec2_vm_instance_created_and_connected_via_PuTTY

ec2_vm_instance_installed_git

ec2_vm_instance_installed_npm_and_nodejs

ec2_vm_running_port_3000(client)_8080(server)

mongodb_atlas_network_ip_set

ec2_inbound_rules_set

deployed_website

deployed_website_after_crud

What we did -

  1. We hosted our MERN stack app on AWS on EC2 VM (using PuTTy to connect to VM)
  2. In 2nd attemp, we dockerized the app and then deployed it on EC2 VM
  3. Use Kubernates for container orchestration, to handle the scaling part, then try to add load balancing to it
  4. Use Terraform cli to interact with aws console

Resources -

  1. Host MERN app on EC2 - https://www.youtube.com/watch?v=xQshKLy0K4M , https://petri.com/install-git-ubuntu , https://linuxize.com/post/how-to-install-node-js-on-ubuntu-18.04/
  2. ChatGPT😉

Elastic ip address - reamins same after stopping and restarting the VM, it have it's own charges. Elastic address is ipv4, not ipv6 and you can use it to connect to your instance, whereas public ip address will keep on changing.