SHRI RAMDEOBABA COLLEGE OF ENGINEERING AND MANAGEMENT

Department of Computer Science & Engineering

Session: 2021-22

CLOUD COMPUTING (CST452-4)

ASSIGNMENT

VII Semester, B.E.

Shift-II

Group Members

Aradhita Menghal (04)

Ketki Fadnavis (05)

Shreyas Nemani (77)

Course Coordinator

Prof. Heena Agrawal

Statement: Creation of EC2 instances and establishing ping communication between two EC2
instances in AWS Cloud.

Abstract:
Amazon Elastic Compute Cloud (Amazon EC2) provides scalable computing capacity in the
Amazon Web Services (AWS) Cloud. Using Amazon EC2 eliminates your need to invest in
hardware upfront, so you can develop and deploy applications faster. You can use Amazon EC2
to launch as many or as few virtual servers as you need, configure security and networking, and
manage storage. Amazon EC2 enables you to scale up or down to handle changes in
requirements or spikes in popularity, reducing your need to forecast traffic.

The instance is an Amazon EBS-backed instance (meaning that the root volume is an EBS
volume). You can either specify the Availability Zone in which your instance runs, or let
Amazon EC2 select an Availability Zone for you. When you launch your instance, you secure it
by specifying a key pair and security group. When you connect to your instance, you must
specify the private key of the key pair that you specified when launching your instance.

Tools and language used: AWS Cloud

Introduction:
An instance is a virtual server in the AWS Cloud. With Amazon EC2, you can set up and
configure the operating system and applications that run on your instance.

Amazon EC2 provides the following features:

● Virtual computing environments, known as instances

● Preconfigured templates for your instances, known as Amazon Machine Images (AMIs),
that package the bits you need for your server (including the operating system and
additional software)
● Various configurations of CPU, memory, storage, and networking capacity for your
instances, known as instance types
● Secure login information for your instances using key pairs (AWS stores the public key,
and you store the private key in a secure place)
● Storage volumes for temporary data that are deleted when you stop, hibernate, or
terminate your instance, known as instance store volumes
● Persistent storage volumes for your data using Amazon Elastic Block Store (Amazon
EBS), known as Amazon EBS volumes
 ● Multiple physical locations for your resources, such as instances and Amazon EBS
volumes, known as Regions and Availability Zones
● A firewall that enables you to specify the protocols, ports, and source IP ranges that can
reach your instances using security groups
● Static IPv4 addresses for dynamic cloud computing, known as Elastic IP addresses
● Metadata, known as tags, that you can create and assign to your Amazon EC2 resources
● Virtual networks you can create that are logically isolated from the rest of the AWS
Cloud and that you can optionally connect to your own network, known as virtual private
clouds (VPCs)

Implementation:

Steps to Create EC2 Instance:

1. La ances

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. From the console dashboard, choose Launch Instance.

3. The Choose an Amazon Machine Image (AMI) page displays a list of basic
configurations, called Amazon Machine Images (AMIs)

4. .On the Choose an Instance Type page, you can select the hardware configuration of your
instance. Select the t2.micro instance type, which is selected by default. On the Choose
 an Instance Type page, choose Review and Launch to let the wizard complete the other
configuration settings for you.

5. On the Review Instance Launch page, under Security Groups, you'll see that the wizard
created and selected a security group for you. You can use this security group, or
alternatively, you can select the security group that you created when getting set up using
the following steps:
○ Choose Edit security groups.

○ On the Configure Security Group page, ensure that Select an existing security
group is selected.
○ Select your security group from the list of existing security groups, and then
choose Review and Launch.

6. On the Review Instance Launch page, choose Launch.

7. When prompted for a key pair, select Choose an existing key pair, then select the key pair
that you created when getting set up. If you launch your instance without a key pair, then
you can't connect to it.
8. When you are ready, select the acknowledgment check box, and then choose Launch
Instances.
9. A confirmation page lets you know that your instance is launching. Choose View
Instances to close the confirmation page and return to the console.
10. On the Instances screen, you can view the status of the launch. It takes a short time for an
instance to launch. When you launch an instance, its initial state is pending. After the
instance starts, its state changes to running and it receives a public DNS name. (If the
Public IPv4 DNS column is hidden, choose the settings icon ( ) in the top-right
corner, toggle on Public IPv4 DNS, and choose Confirm.
11. It can take a few minutes for the instance to be ready so that you can connect to it. Check
that your instance has passed its status checks; you can view this information in the
Status check column.
 2. Connect to the Instances
To connect to your Windows instance using an RDP client

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, select Instances. Select the instance and then copy the Public Ipv4
address.

3. In your System, go to ‘Run’ and type mstsc, you will see a Remote Desktop Connection
Console. Paste the public Ip address and click ok.
4. After the Connect ‘Windows Security’ box will appear asking for Username and
Password. In the Username field type ‘administrator’
5. For getting Password, go to the Connect to instance page, choose the RDP client tab, and
then choose ‘ Get password’.
6. Choose Browse and navigate to the private key (.pem) file you created when you
launched the instance. Select the file and choose Open to copy the entire contents of the
file to this window.
7. Choose Decrypt Password. The console displays the default administrator password for
the instance under Password, replacing the Get password link shown previously. Save the
password in a safe place. Copy and paste the password in the ‘Windows Security’ box
and Click on Ok.
8. RDP connection of your EC2 instance will open.
9. Repeat steps 1 to 8 similarly for the second EC2 instance.
10. Go to the RDP of both instances and go to ‘Run’ and type firewall.cpl

11. In the Windows Firewall dialog box, turn off the Firewall of both instances.
12. In the Command Prompt of both instances type ipconfig for finding the Private Ip
address
13. In the Command Prompt of instance one type ‘ping Ip address -t’ where Ip address will
be the Private Ip address of another instance obtained from previous steps.
References:

● https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/concepts.html