Changes

** Create new Route table ops345-route-tableWe'll make a VM named router. It won't do much routing, but it will give us more practice with basics. == Security group == Your network environment is now done, add route but before you create your next VM: make a security group for 0it.0Just like you did in the previous lab.0.0/0 through ops345-internet-gateway. Then add explicit subnet association to subnet-ops345 * The Security groups are back in the EC2 Management Console** Call it ops345routersg** Create Since a new security description is required, give it something like "Security group for router instance"ops345sg" ** It will be in the vpc-ops345 with only VPC.** Only the SSH server port (TCP 22) is to be openfor inbound connections, from anywhere in the world. == Create VM == * Create a new VM (instance) named "router", in . The process is almost identical to the "ops435-first" VM from the last lab.** In your new vpc/VPC and subnet, with ** With primary IP 10.3.45.10 (first 4 addresses on AWS subnet are not usable), default ** Default storageoptions** With security group ops345routersg** Using your existing key ops345-first-key, ops345sgunless you lost that already.** == Configure VM == Follow the instructions in lab 1 to set up your user, except use the subnet-ops345 and ops345sg and assign private ip 10.3.45.10. Also create a new key called ops345-all-aws-machines