• AWS Deployment using AWS CLI
  • Table of Contents
  • Description
    • Folder structure
    • File description
    • AWS Infrastructure created
  • Pre-deployment
  • Deploy infrastructure and application
  • Destroy infrastructure and application

The repo has scripts to a Node.js image processing web application connected to a MYSQL AWS RDS, and two s3 buckets.
The application is deployed on to two AWS EC2 Ubuntu instances behind a Internet Gateway, AWS virtual private cloud, two subnets, and a Elastic Load Balancer utilizing two subnets.

midterm
├── README.md
├── scripts
│ ├── run.sh
│ └── templates
│ ├── create-env.sh
│ ├── destroy-env.sh
│ └── install-app-env.sh
└── web-app

• run.sh gets user input and provide the variables to each template file.
• create-env.sh create aws infrastructure.
• install-app-env.sh clones repo and start node app.
• destroy-env.sh1 destroys the previously created AWS infrastructure.

• 1 internet gateway
• 1 VPC
• 2 Subnets
• 1 Security group
• 2 s3 buckers
• 1 DB subnet
• 1 RDS MYSQL instances
• 1 Target group
• 1 ELB application load balancer
• 2 EC2 instances

• Must have awscli properly setup.
• Need a EC2 instance keypair.
• Need a EC2 instance profile for AWS EC2 service with at least S3 and RDS full privileges.
• Line endings for shell scripts must be LF.
• Keypair must exist in region you choose.

Note: Github deployment key is preseeded in AMI image w/ git, nodes, and aws installed.

• Must be linux/Unix environment
• Run run.sh script
• Load Balance DNS name is returned at the end of the script, will take a couple seconds to propagate.

• Run destroy.sh script