3 parts of one problem

You work for a start-up company and you are asked to spin-up 3 virtual machines (EC2s). Each EC2 is for specific purpose. - The first machine is for a web server. - The second is for general purpose. - The third one is reserved for internal use only and not accessible from the outside. At this point the company just need a simple network so you only use the AWS default VPC. Any configurations not mentioned in the problem means it is for you to decide. All EC2 are to have: - Instance type:t2.micro. - AMI: ubuntu. 1. First EC2 (Web Server) - Name it your_lastname1 - Setup: - ssh from everywhere - Has a public IP - Allow ping from everywhere - Allow http call from everywhere - Install nginx - modify so it will say in the first line: "This is 'your-first and last name" 2. Second EC2 (General purpose) - Name it your_lastname2 - Set-up: - ssh from everywhere - has a public IP - there is a concerned about Ping Of Death (POD) so you want to allow ping from your laptop only 3. Third EC2 (Internal use only) - Name it your_lastname3 - You want to reserve and protect this EC2 for special program that can not be accessed from the outside. Setup: - ssh from your first EC2 only - No public IP - Allow ping from your first EC2 only The 1st EC2 is the bastion host for the 3rd EC2. To connect the 3rd EC2 (for example to do ping command from the 3rd EC2) do: - Do ssh connection to the first EC1. I suggest to use SSH client instead of EC2 instance connect. - We have to copy the private key (.pem) to the first EC1 so that it can connect to the 3rd EC2. The easiest way is to use the nano editor and create a file with the same name as the .pem file you saved in your laptop, then copy and paste it to that document. Do Ctrl O, enger, Ctrl X. - use ssh command as suggested in the EC2 console connect for the 3rd EC2