Skip to content

Latest commit

 

History

History
142 lines (118 loc) · 5.87 KB

README.md

File metadata and controls

142 lines (118 loc) · 5.87 KB

it366 setup

Linux Recommended

  • It is highly recommended that you use a Linux machine to setup the following
  • If you do not have one, you can install a Linux virtual machine inside VMware and setup everything using the vm

Pre-requisites

Install AWS Command Line Tool and Terraform

Linux

  • Open Command Prompt in Ubuntu - or your command prompt on Linux/Mac
  • Add unzip (it is already installed on Mac)
    • sudo apt install unzip -y
  • Install AWS CLI
    • curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
    • unzip awscliv2.zip
    • sudo ./aws/install
    • aws --version
  • Add $HOME/.local/bin to path 
    • vim .bashrc
    if [ -d "$HOME/.local/bin" ] ; then
        PATH="$HOME/.local/bin:$PATH"
    fi
source .bashrc
  • Install Terraform
    • curl "https://releases.hashicorp.com/terraform/0.14.4/terraform_0.14.4_linux_amd64.zip" -o "terraform.zip"
    • unzip terraform.zip
    • sudo mv terraform /usr/local/bin/
    • terraform --version

Windows

Logging in to AWS Educate and Get the Keys

  • Log in to https://www.awseducate.com

  • Click the My Classrooms link

  • Click the Go to classroom button alongside your desired classroom

  • Under the Your AWS Account Status area, click the Account Details button

  • Show the AWS CLI information - copy this into your ~/.aws/credentials file

    • Open WSL
    • mkdir ~/.aws
    • vim ~/.aws/credentials 
      •   [default]
  aws_access_key_id=QWERTYUIOPASDFGHJKL
  aws_secret_access_key=tHisIsnOtanActUal/Key
  aws_session_token=Vy0suaL4NT1PrSLaPLZAT8fgbNpwhw07ByUvBZ6F0BSITkbUyrIOFUdQu6HDYVhskoQt4OGvTzi0PdLQwvI8FNnMrkESlFxeLSxVy0suaL4NT1PrSLaPLZAT8fgbNpwhw07ByUvBZ6F0BSITkbUyrIOFUdQu6HDYVhskoQt4OGvTzi0PdLQwvI8FNnMrkESlFxeLSxVy0suaL4NT1PrSLaPLZAT8fgbNpwhw07ByUvBZ6F0BSITkbUyrIOFUdQu6HDYVhskoQt4OGvTzi0PdLQwvI8FNnMrkESlFxeLSx
    • ATTENTION: The token generated renews quickly. Make sure you do not wait too long to start setting up everything, otherwise an error will appear.

  • Click the AWS Console button to log into the console.

    • At the top right; ensure the region you are in is N. Virginia

Part One Setup

Terraform Infrastructure

  • mkdir ~/GitRepos
  • cd ~/GitRepos
  • git clone https://github.com/jgiboney/ITC-366.git
  • cd ITC-366/partOne
  • terraform init
  • terraform apply
  • Accept the changes yes
  • If Terraform complains about credentials, go back to the Logging in to AWS Educate and Get the Keys section and re-create your ~/.aws/credentials file
  • This will take a few minutes, but you should see the infrastructure appear in the AWS Console.
  • The output from the terraform will give you details for logging in to the NAT Instance and the Linux Instance
    • chmod the PEM file
      • chmod 400 my-key.pem
    • ssh into the NAT instance
    • log out of the NAT instance
      • exit
    • use the tunnel script to log into the private linux instance via the NAT
    • check that NAT is setup correctly
      • ping google.com
  • If the above commands do not work for ssh connections, try using the following format instead
    • All of the information of your instance can be found on AWS EC2.
      • ssh -i "[publicKey.pem]" [your username]@[your public ipv4 DNS]
    • The command should look something like this:
  • Once you are finished, you can use terraform destroy to remove the entire infrastructure if you want.

Part Two Setup

  • Infrastructure in this part does not collide with part 1. They can run together or separately.
  • You DO NOT need to destroy everything in part one to run part two.

Terraform Infrastructure

  • Navigate to your GitHub folder that you cloned from part one
  • cd partTwo
  • terraform init
  • terraform apply
  • Accept the changes yes
  • If Terraform complains about credentials, go back to the Logging in to AWS Educate section and re-create your ~/.aws/credentials file
  • This will take a few minutes, but you should see the infrastructure appear in the AWS Console.

Routing in AWS

  • Part Two creates three subnets in AWS
    • 172.31.101.0/24
    • 172.31.102.0/24
    • 172.31.103.0/24
  • And three EC2 instances
    • 2 Clients in the 101 and 102 subnets
    • 1 Router in the 103 Subnet
  • Security Groups
    • 101 and 102 can only talk to the router

Try the following if your machines cannot ping each other

  • Turn on IP Forwarding on the router (SSH into the router)
echo 'net.ipv4.ip_forward=1' | sudo tee -a /etc/sysctl.conf
sysctl -p /etc/sysctl.conf
  • Add routes to the route tables in the clients (SSH into the clients). Change the x, y, and z depending on the client and instance.
sudo route add -net 172.31.10x.0 netmask 255.255.255.0 gw 172.31.y.z

Note

  • Source/Destination Checks must be turned off for the router and the added network cards for traffic to flow
source_dest_check = false
  • Once you are finished, you can use terraform destroy to remove the entire infrastructure.

Resources for Mac users