Vist this link https://awsacademy.instructure.com/
Username: for assigned writer
Password:
Please see attached document
Screen shot needed
Hands-On: AWS – Creating a Simple VPC10 POINTS
In this exercise, you will be creating a simple Virtual Private Cloud (VPC). As part of this exercise, you will be creating a subnet and accepting defaults for IP addresses and the Internet Gateway. Watch the video first and then follow the subsequent steps to create your simple VPC.
Watch the video below and follow the prompts.
NOTE: The AWS interface changes over time. The instructions below will provide an overview of the steps needed to complete this assignment. But this document tracks more closely with the current interface.
Create a Simple VPC
Follow these instructions to create a simple VPC.
1. Login to your AWS Educate Account, select your classroom, and then the AWS Console.
2. Select VPC from the available services using the menu at the top left of the screen
3. Launch the VPC Wizard by selecting the Launch VPC Wizard button at the top left – this will guide us through the process of creating a simple VPC.
4. The first step using the wizard is to select our VPC configuration – since we will be creating a simple VPC select the first box in the list of boxes on the left of the screen.
5. Then click the box labeled Select from the mid-left of the screen to continue.
6. We now need to provide a name for our VPC and for a Subnet that will reside within our VPC.
a. Provide a Name in the box labeled VPC name.
b. Provide a Name for your subnet in the box labeled Subnet Name.
c. When finished click the box labeled Create VPC on the mid-right of the screen to continue.
7. You should see a message that your VPC has been successfully created – review the message and then click the small box labeled OK near the top right.
8. You are now on the VPC Dashboard and should see your new VPC as well as a default VPC that AWS provides.
a. You can confirm the status of your VPC by scrolling to the right. You will see the word No under the column heading of Default VPC.
b. Scroll back to the left.
9. Our next step is to add a Security Group which will act as a virtual firewall to our VPC.
a. Select Security Groups from the left side menu. It is located near the bottom of the menu list.
10. You will notice that we have several Security Groups available to us by default. We will create a new Security Group by clicking the box labeled Create Security Group near the top left of the screen.
11. Enter a name for your security group in the box labeled Security Group Name. You must also provide a descriiption.
12. Using the dropdown arrow on the box labeled VPC select your name.
13. Click the box labeled Create located near the mid-right of the screen – you will next see a screen that confirms success.
a. Click the box labeled Close in the middle-right of the screen.
14. You are now back to the Security Group page where we now need to add rules to our Security Group. Remember that a Security Group is like a virtual firewall. We need to specify the rules to permit or deny traffic into our VPC.
15. Select the checkbox for your Security Group Name.
a. Click the tab near the bottom of the page labeled Inbound Rules.
b. Notice that there are no rules defined for our Security Group.
16. Select the box labeled Edit Rules to create a rule for our Security Group.
17. We are going add three (3) rules to our Security Group.
a. Rule 1:
Click the box labeled Add Rule.
Select the arrow on the dropdown menu under the Title column.
Scroll down to find HTTP in the list and select it.
Notice that the Protocol and Port Range populate.
We are going to add a CIDR block (although we could accept the default).
Enter 0.0.0.0/0 for the CIDR block. In this exercise, we will use this for all of all rules.
Add a descriiption of your choice in the Descriiption block.
Click the box labeled Add Rule on the left to continue.
b. Rule 2:
Select the arrow on the dropdown menu under the Title column.
Scroll down to find HTTPS in the list and select it.
Notice that the Protocol and Port Range populate.
We are going to add a CIDR block (although we could accept the default).
Enter 0.0.0.0/0 for the CIDR block. (In this exercise, we will use this for all of all rules).
Add a descriiption of your choice in the Descriiption block.
Click the box labeled Add Rule on the left to continue.
c. Rule 3:
Select the arrow on the dropdown menu under the Title column.
Scroll down to find SSH in the list and select it. This rule will allow us to use PuTTy to access our servers via SSH.
Notice that the Protocol and Port Range populate.
We are going to add a CIDR block (although we could accept the default).
Enter 0.0.0.0/0 for the CIDR block. In this exercise, we will use this for all of all rules.
Add a descriiption of your choice in the Descriiption block.
Click the box labeled Save Rule on the lower right of the screen to continue.
You will see a confirmation screen letting you know that you’ve successfully created Inbound Security Group Rules.
Click the box labeled Close in the middle right to continue.
d. You are now again on the Security Group page. If not checked, select the checkbox for the Security Group we’ve created and scroll down to view the new inbound rules.
Note that we could also create outbound rules however, we will not do so in this exercise.
18. Our next step is to create an EC2 instance and to associate it with our new VPC.
19. Select Services from the menu at the top of the screen and then select EC2.
20. The following steps should be somewhat familiar to you. Select the box labeled Launch Instance from the middle left of the screen.
21. We will use the first AMI (Amazon Machine Image). Click the box labeled Select on the right for the first Amazon Linux image available to us.
22. We will accept the default General Purpose Instance Type t2.micro. Click the box labeled Next: Configure Instance Details on the lower right.
23. This is where we will associate our new instance with our new VPC and subnet. The names of each should appear in the appropriate drop-down menu lists.
a. Use the arrow to open the drop-down menu for Network and select your VPC by the name you assigned earlier.
b. Then do the same for the Subnet.
c. Once down click the box labeled Next: Add Storage on the lower right of the page.
24. We will accept the defaults on the Add Storage page. Click the box labeled Next: Add Tags on the lower right of the page.
25. Add a tag to your new instance. This will help you distinguish it from other instances that you’ve created.
a. In the box labeled Key enter Name.
b. In the box labeled Value enter any descriiptive name of your liking.
c. Then click the box labeled Next: Configure Security Settings Group on the lower right of the page.
26. Now we will associate our instance with our new Security Group.
a. Select the radio button labeled Select and existing security group in the middle top of the page.
b. Your newly created Security Group should appear.
c. Select the checkbox for your Security Group – notice that the rules now appear.
27. Notice that Amazon warns us that we’ve left ourselves open to the world. This is because we used 0.0.0.0/0 as our CIDR block. This is fine for our purposes.
28. Click the box labeled Launch on the lower right of the page.
29. You will now see a pop-up window that will permit us to select an existing key pair to associate with our new instance.
a. In the first box select the drop-down menu for Choose and existing key pair.
b. Then in the Select a key pair box use the drop-down menu to select the key pair that you created in an earlier exercise (If your key pair does not appear in the list you will need to refer back to the earlier exercise to create a key pair).
c. Check the box to acknowledge that you have access to your key pair and then select the box labeled Launch Instances.
d. You will see a confirmation screen – select the box labeled View Instances at the lower right.
e. It takes up to a minute for your instance to launch. You will see the status change to running when it is ready
30. We have one more step. We are going to set up Elastic IPs. If you recall AWS will provide new public IP addresses each time we launch an instance. By using Elastic IP addresses we essentially reserve addresses that will not change at each launch of our instances.
a. Scroll down on the left menu to find Elastic IPs and select that link.
b. On the resulting page click the box labeled Allocate new addresses.
c. We are going to use addresses from Amazon’s pool so be sure that the radio button for Amazon pool is selected.
d. Select the box labeled Allocate on the mid-right of the screen.
e. The resulting screen should say that the request has succeeded. Select the box labeled Close to continue.
f. Notice on the subsequent screen that we now have an Elastic IP address for our VPC.
31. We now need to associate our Elastic IP address space to our other AWS resources.
a. Using the down arrow in the box labeled Actions, scroll down and select the menu item Associate address.
b. Use the drop-down arrow to open the menu beside Instance and select the name of your newly created instance from the list.
c. Select the box labeled Associate on the lower right.
d. A screen appears confirming success. Select the box labeled Close.
32. Notice on the Elastic IP page that our Public DNS name now includes our Elastic IP address.
33. Let’s return to our EC2 Dashboard. Select EC2 Dashboard from the menu on the left. It will be at the top of the list.
34. Your instance should be running so select the like titled Running Instances near the top of the page.
35. Now take a screen capture of this page to submit to the dropbox.
36. Let’s connect to our instance using SSH.
a. Copy the Public DNS name to the clipboard using the Notepad item beside the Public DNS (IP4) line near the bottom right of the screen.
b. Launch PuTTY.
Paste the Public DNS name into the Host Name box.
Scroll the left in this box and add “ec2-user@” to the front of the Public DNS name so that the Host Name is ec2-user@yourpublicDNSName.
Select SSH and the Auth from the menu on the left.
Select Browse to select your Private key file. Find your previously saved file (remember it should be a .ppk file).
Select the box labeled Open near the bottom of the PuTTY Window.
Click Yes on the pop-up dialog box.
We are now connected through our Security Group firewall. Note, we would not have been able to connect if we had not added the inbound rule to our Security Group.
At this point, you can execute any Linux command. Feel free to experiment and enter exit when done to terminate your session.
37. Finally, let’s clean up all that we just created. In a production environment we would keep our servers running and our VPCs, etc. in place. But in this exercise, we will delete the instance and the VPC.
38. Delete the Instance
a. First, we return to the EC2 Dashboard by selecting the link at the top of the left side menu.
b. Select the link for VPC.
c. On the resulting warning screen click the drop-down arrow to the left of Release attached Elastic IPs.
d. Make sure that you’ve checked the box to release the Elastic IPs. Again, we would keep these in place if we were in a production mode.
e. Then select Yes, Terminate at the lower right.
39. Delete the VPC.
a. Select Services from the menu at the top of the page.
b. Select the link for VPC.
c. Select Your VPCs from the menu on the left.
d. You are now on the VPC dashboard. Select the checkbox next to your VPC.
e. From the Actions menu select the down arrow and then the first option Delete VPC.
f. AWS will display a dialog box to ensure that you wish to delete the VPC. Click the box labeled Delete VPC at the lower right.
g. A dialog box will appear to confirm the deletion. Click the box labeled Close.
h. Then return to the Services menu by selecting Services from the top menu.
40. Let’s check on our EC2 instances.
a. Select EC2 from the Services page.
b. Select Instances from the menu on the left.
c. You should see an instance state of Terminated.
41. This completes the exercise. Logoff as you normally would.
Guidelines
Submit the following items to the Module 6.1 Dropbox:
• Screen capture of your trail name and S3 Bucket.
