Scribd
Upload
34 views8 pages

0052 CC 1

SPPU TE CC assignment 1

Uploaded by

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

0052 CC 1

SPPU TE CC assignment 1

Uploaded by

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

LP-2: Cloud Computing

Assignment No. 01

A Case study on Amazon EC2 and learn about Amazon EC2 web services.

Theory:
An EC2 instance is nothing but a virtual server in Amazon Web services terminology. It stands for Elastic Compute Cloud. It is a
web service where an AWS subscriber can request and provision a compute server in AWS cloud. An on-demand EC2 instance is
an offering from AWS where the subscriber/user can rent the virtual server per hour and use it to deploy his/her own
applications. The instance will be charged per hour with different rates based on the type of the instance chosen. AWS provides
multiple instance types for the respective business needs of the user.
Thus, you can rent an instance based on your own CPU and memory requirements and use it as long as you want. You can
terminate the instance when it’s no more used and save on costs. This is the most striking advantage of an on-demand
instance- you can drastically save on your CAPEX. Let us see in detail how to launch an on-demand EC2 instance in AWS:

Step 1: Logging in to your AWS Account

Once logged in, navigate to EC2 tab from ‘View all services’. Click on

Step 2: Naming your EC2 Instance


You can give any name to your EC2 instance. Here, we name our EC2 instance to ‘myFirstServer’.

Step 3: Selecting OS type and AMI


Here, we need to select the type of OS to RUN our instance. We continue with the default OS ‘Amazon Linux’ that is also available
under Free Tier. The default architecture is set to 64-bit (x86).
Step 4: Selecting the type of Instance
The instance type is set according to your region and zone. Here, we get the default instance type as ‘t2.micro’ which is also
available under Free Tier; hence, we do not change the instance type.

Step 5: Creating a new key-pair name


A key pair allows us to connect to our instance securely using local terminal. We enter key pair name as ‘myWebServer-01’ to
easily identify our first instance. Rest parameters like key pair type and format are kept as it is. Once done, we click on ‘Create key
pair’.
A file ‘myWebServer-01.pem’ will be downloaded that we will use to access our instance remotely. This key must be kept secure
and easily accessible for further use.

Step 6: Changing Network Settings


In addition to SSH traffic, we would also like to allow HTTP and HTTPS traffic. Hence, we check these two boxes while keeping the
rest of network settings as it is.
Step 7: Assigning Storage to our EC2 Instance
All the default storage settings that are covered in Free Tier have been already applied. Hence, we do not make any changes here
and keep the values as it is.

Step 8: Launching the EC2 Instance

Once we are done with all the steps above, we click on


Before launching the instance, make sure you have Number of instances = 1 in the Summary section. The following screen shows
the progress of instance creation.

Once the instance has been created, we get a Success dialog as shown. We click on the instance ID shown in the dialog to know
more about this instance.

Step 9: Accessing the created Instance


Once an instance has been created, we can access it in the ‘Instances’ tab. To know more about an instance, we click on ‘Instance
ID’.

The following tab opens when we click on ‘Instance ID’ of an instance.

In this way, we have successfully created an instance named ‘myFirstServer’!


Step 10: Connecting to an Instance using Terminal
You can connect to your created instance using ‘Connect’ tab present at the top side of the instance dashboard. Here, we connect
to our instance using SSH Client. Copy the commands shown in SSH Client dialog box.

Steps 11: Connecting to your Instance using its Public DNS


Locate the file ‘myWebServer-01.pem’ downloaded in step 5 and open the parent folder in Terminal.

Steps 12: Understanding CPU utilization by the Instance

Step 13: Checking OS Version


Step 14: Memory Utilization by the Instance

Step 15: Finding Free Memory inside the Instance

Step 16: Stopping an Instance


You can stop an instance temporarily by selecting ‘Stop instance’ from the ‘Instance state’ tab. This instance can be started again
when required. Stopping an instance lets you prevent it from running unnecessarily thereby preventing additional charges.

Conclusion:
In this way, we created an on-demand EC2 instance using AWS Console.

You might also like