Scribd
Upload
19 views26 pages

20i0551 - Muhammad Usman - Lab02

Uploaded by

Muhammad usman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views26 pages

20i0551 - Muhammad Usman - Lab02

Uploaded by

Muhammad usman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 26

CLOUD COMPUTING LAB 1.

2
ASSIGNMENT 2
Muhammad Usman 20i0551

FEBRUARY 18, 2024


Task 1: Create Your VPC
4. In the search box to the right of Services, search for and choose VPC to open the
VPC console.

5. Begin creating a VPC.

In the top right of the screen, verify that N. Virginia (us-east-1) is the region. Choose the
VPC dashboard link which is towards the top left of the console.Next, choose Create
VPC.
6. Configure the VPC details in the VPC settings panel on the left.

7. In the Preview panel on the right, confirm the settings you have configured.
8. At the bottom of the screen, choose Create VPCThe VPC resources are created. The
NAT Gateway will take a few minutes to activate. Please wait until all the resources are
created before proceding to the next step.
9. Once it is complete, choose View VPC.The wizard has provisioned a VPC with a
public subnet and a private subnet in one Availability Zone with route tables for each
subnet. It also created an Internet Gateway and a NAT Gateway.

Task 2: Create Additional Subnets


10. In the left navigation pane, choose Subnets.First, you will create a second public
subnet.

11. Choose Create subnet then configure.


12. Choose Create subnet.The second public subnet was created. You will now create
a second private subnet.

13. Choose Create subnet then configure.


14. Choose Create subnet.The second private subnet was created.

15. In the left navigation pane, choose Route tables.


16. Select the lab-rtb-private1-us-east-1a route table.

17. In the lower pane, choose the Routes tab.Note that Destination 0.0.0.0/0 is set to
Target nat-xxxxxxxx. This means that traffic destined for the internet (0.0.0.0/0) will be
sent to the NAT Gateway. The NAT Gateway will then forward the traffic to the internet.
18. Choose the Subnet associations tab.You created this route table in task 1 when
you chose to create a VPC and multiple resources in the VPC. That action also created
lab-subnet-private-1 and associated that subnet with this route table.

19. In the Explicit subnet associations panel, “Edit Subnet Assosiations”


20. Leave lab-subnet-private1-us-east-1a selected, but also select lab-subnet-
private2.

21. Choose Save associations. You will now configure the Route Table that is used by
the Public Subnets.
22. Select the lab-rtb-public route table (and deselect any other subnets).

23. In the lower pane, choose the Routes tab.Note that Destination 0.0.0.0/0 is set to
Target igw-xxxxxxxx, which is an Internet Gateway. This means that internet-bound
traffic will be sent straight to the internet via this Internet Gateway.
24. Choose the Subnet associations tab.

25. In the Explicit subnet associations area, choose “Edit Subnet Assossiation.”
26. Leave lab-subnet-public1-us-east-1a selected, but also select lab-subnet-
public2.

27. Choose Save associations.Your VPC now has public and private subnets
configured in two Availability Zones. The route tables you created in task 1 have also
been updated to route network traffic for the two new subnets.
Task 3: Create a VPC Security Group

28. In the left navigation pane, choose Security groups.

29. Choose Create security group and then configure.


30. In the Inbound rules pane, choose “Add Rule.”

31. Configure the following settings.


32. Scroll to the bottom of the page and choose Create security group.You will use
this security group in the next task when launching an Amazon EC2 instance.

Task 4: Launch a Web Server Instance

33. In the search box to the right of Services, search for and choose EC2 to open the
EC2 console.
34. From the Launch instance menu choose Launch instance.

35. Name the instance. Give it the name Web Server 1.


36. Choose an AMI from which to create the instance. In the list of available Quick Start
AMIs, keep the default Amazon Linux selected.
37. Choose an Instance type. In the Instance type panel,keep the default t2.micro
selected.

38. Select the key pair to associate with the instance. From the Key pair name menu,
select vockey.
39. Configure the Network settings.Next to Network settings, choose Edit, then
configure.

40. In the Configure storage section, keep the default settings.


41. Configure a script to run on the instance when it launches. Expand the Advanced
details panel. Scroll to the bottom of the page and then copy and paste the code shown
below into the User data box.

42. At the bottom of the Summary panel on the right side of the screen choose Launch
instance.You will see a Success message.
43. Choose View Instances.

44. Wait until Web Server 1 shows 2/2 checks passed in the Status check column.This
may take a few minutes. Choose the refresh icon at the top of the page every 30
seconds or so to more quickly become aware of the latest status of the instance.
45. Select Web Server 1.

46. Copy the Public IPv4 DNS value shown in the Details tab at the bottom of the
page.
47. Open a new web browser tab, paste the Public DNS value and press Enter.You
should see a web page displaying the AWS logo and instance meta-data values.

Grade Report:

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy