Launch an EC2 instance.
Connect to a running EC2 instance using Secure Shell (SSH).
Create a custom configured AMI.
Launch an EC2 instance from the custom configured AMI.
Alter instances as directed.
Requirements
Create a new Security Group for both EC2 instances to use that:
Allows HTTP from the entire internet.
Allows SSH from a single IP (your IP). (The EC2 Instance Connect feature will not work.)
Launch an Amazon Linux 2 EC2 instance.
This instance should use the Amazon Linux 2 AMI for a boot image.
This instance should be built using a t2.micro instance.
The network firewall should use your custom Security Group.
The boot volume should be 10 GB gp3 (the default is 8 GB gp2).
Customize this instance with instance user data to install your web server software.
Add a Tag with the key of "Server" and the value of "First".
Connect to a running EC2 instance using SSH and the .pem key file.
Create an AMI of a system that has been custom configured with your web server already installed.
Launch a second EC2 instance from the custom-created AMI.
This instance should be built using a t2.micro instance.
The network firewall should use your custom Security Group.
The boot volume should also be 10 GB gp3 (the default is 8 GB gp3 this time).
Add a Tag with the key of "Server" and the value of "Second".
Set a lifecycle policy for EBS storage to back up both instances every hour and keep three snapshots.
Add a second EBS volume to the second EC2 instance during or after creation. Mount this second volume to /data.
Use the EC2 Console filters to display instances selectively.
Use the EC2 Console customize feature to remove unwanted columns.
Deliverables
Your Lab Submission Word Document, including:
Screenshot of the EC2 instances grid that show the two instances you created.
Screenshot of the EC2 instances grid filtered to show only one of the instances you created and no IPs or DNS names in that view.
Screenshot or paste the User Data used on the first instance to install the web server.
Screenshot of the second instance's details with the following data highlighted: Instance type, Public IPv4 address, Private IPv4 address, Public IPv4 DNS, AMI name.
Screenshot of the second instance's Security tab details: Inbound and Outbound rules.
Screenshot of the second instance's Storage tab details: Block devices attached.
Screenshot of the second instance's Tags tab details: Tags attached.
Screenshot of the EBS Lifecycle policy you created for both instances to create hourly snapshots showing details and schedules.
Screenshot showing the webpage of your second instance through a browser. Be sure the IP is visible.
Screenshot showing your public IP reported from a web-based IP indication service, e.g., whatsmyip.com.
Screenshot of the Security Group you created for both instances showing the Inbound and Outbound rules.
Screenshot of an EC2 Instance connect session on one of your instances showing that it cannot connect.
Screenshot of an SSH session on your second instance showing what files are in the additional volume you mounted at /data, e.g., ls -l /data.
Screenshot of an SSH session on your second instance showing the output of the mount command showing how /data is mounted.
Screenshot showing either the .ssh folder showing the keys you have or the config of an SSH program showing connection parameters.
Screenshot of the AMI details you created from the first server.