CASE STUDY ON

AMAZON EC2

SUBMITTED BY

Tanvi Rajendra Patil

Roll No :- 183726

T.Y.BSC COMPUTER SCIENCE

VIKAS COLLEGE OF ART'S ,SCIENCE & COMMERCE

Vikharoli (East)

UNDER GUIDENCE BY
MRS.Vikay SIR

UNIVERSITY OF MUMBAI
2018-2019
 INTRODUCTION OF AMAZON EC2

Amazon Elastic Compute Cloud (EC2)

Amazon EC2 is a compute web service that offers secure, resizable compute capacity in the
cloud. It is designed for scalable deployments and optimizing your workloads.

Use Amazon EC2 for…

• Enterprise applications
• HPC, Big Data, and Analytics workloads (e.g. Hadoop, Spark)
• Migrations from on-premises environments, including BYOL
• Application modernization

Elastic IP addresses allow you to allocate a static IP address and programmatically assign it
to an instance. You can enable monitoring on an Amazon EC2 instance using Amazon
CloudWatch2 in order to gain visibility into resource utilization, operational performance,
and overall demand patterns (including metrics such as CPU utilization, disk reads and
writes, and network traffic). You can create Auto-scaling Group using the Auto-scaling
feature3 to automatically scale your capacity on certain conditions based on metric that
Amazon CloudWatch collects. You can also distribute incoming traffic by creating an elastic
load balancer using the Elastic Load Balancing4 service. Amazon Elastic Block Storage
(EBS)5 volumes provide network-attached persistent storage to Amazon EC2 instances.
Point-in-time consistent snapshots of EBS volumes can be created and stored on Amazon
Simple Storage Service (Amazon S3)6.
Amazon S3 is highly durable and distributed data store. With a simple web services interface,
you can store and retrieve large amounts of data as objects in buckets (containers) at any
time, from anywhere on the web using standard HTTP verbs. Copies of objects can be
distributed and cached at 14 edge locations around the world by creating a distribution using
Amazon CloudFront7 service – a web service for content delivery (static or streaming
content). Amazon SimpleDB8 is a web service that provides the core functionality of a
database- real-time lookup and simple querying of structured data – without the operational
complexity. You can organize the dataset into domains and can run queries across all of the
data stored in a particular domain. Domains are collections of items that are described by
attribute-value pairs.
 Features of Amazon EC2

Amazon EC2 provides the following features:

 Amazon Relational Database Service9 (Amazon RDS) provides an easy way to setup,
operate and scale a relational database in the cloud. You can launch a DB Instance and
get access to a full-featured MySQL database and not worry about common database
administration tasks like backups, patch management etc.
Amazon Simple Queue Service (Amazon SQS)10 is a reliable, highly scalable, hosted
distributed queue for storing messages as they travel between computers and application
components.

 Amazon Simple Notifications Service (Amazon SNS) provides a simple way to notify
applications or people from the cloud by creating Topics and using a publish-subscribe
protocol.

 Amazon Elastic MapReduce provides a hosted Hadoop framework running on the

web-scale infrastructure of Amazon Elastic Compute Cloud (Amazon EC2) and
Amazon Simple Storage Service (Amazon S3) and allows you to create customized
JobFlows. JobFlow is a sequence of MapReduce steps.

 Amazon Virtual Private Cloud (Amazon VPC) allows you to extend your corporate
network into a private cloud contained within AWS. Amazon VPC uses IPSec tunnel
mode that enables you to create a secure connection between a gateway in your data
center and a gateway in AWS.

 Amazon Route53 is a highly scalable DNS service that allows you manage your DNS
records by creating a HostedZone for every domain you would like to manage.

 AWS Identity and Access Management (IAM) enable you to create multiple Users
with unique security credentials and manage the permissions for each of these Users
within your AWS Account. IAM is natively integrated into AWS Services. No service
APIs have changed to support IAM, and exiting applications and tools built on top of
the AWS service APIs will continue to work when using IAM.
AWS also offers various payment and billing services that leverages Amazon’s payment
infrastructure.
 All AWS infrastructure services offer utility-style pricing that require no long-term
commitments or contracts. For example, you pay by the hour for Amazon EC2
instance usage and pay by the gigabyte for storage and data transfer in the case of
Amazon S3. More information about each of these services and their pay-as-you-go
pricing is available on the AWS Website.
Note that using the AWS cloud doesn’t require sacrificing the flexibility and control
you’ve grown accustomed to:
You are free to use the programming model, language, or operating system
(Windows, OpenSolaris or any flavor of Linux) of your choice.
You are free to pick and choose the AWS products that best satisfy your
requirements—you can use any of the services individually or in any combination.
Because AWS provides resizable (storage, bandwidth and computing) resources, you
are free to consume as much or as little and only pay for what you consume.
You are free to use the system management tools you’ve used in the past and extend
your datacenter into the cloud.

 Who introduce and when means date

EC2 or EC-2 may refer to:

Amazon Elastic Compute Cloud (EC2), a commercial web service for hosting computer
applications

Cardoen EC-2 mine, an anti-personnel mine

Cessna EC-2, a 1930s aircraft

EC2, a district in the London EC postcode area

EC2-S-C1, U.S. World War II Liberty ships

Escadre de Chasse 2, a flight of the French Air Force's Escadron de Chasse 01-002
"Cigognes"

Eurocode 2, an alternative name for European reference norm EN 1992

EC2 or ECII, a musical project produce by Mick Ronson.

 Top Reasons Amazon EC2 Instances Disappear

The fact that Amazon says up-front that computers fail seems to be the number one concern
and criticism of EC2, especially from people who have not used it extensively. I don't
actually spend much time thinking about that because in our experience it's not something to
worry about. It's essential to take into account when designing a system; whenever we set
something up on a machine we immediately think "and what do we do when it fails?" That's a
good thing, not a bad thing, as anyone with production data center experience can attest.

Since it's such a hot topic, I've been keeping a close eye on all the "my instance disappeared"
threads on the EC2 forum, and it's not easy to sort them out. I have no doubt that the vast
majority have to do with operator error:

 trying SSH and forgetting to open port 22 in the security group (or similarly with other ports)
 having difficulties with the SSH keys, or forgetting to set up a key to begin with
 using/constructing an AMI that does not have SSH properly set up
 using/constructing an AMI that does not boot properly (network and/or sshd issues) and
failing to look into console output
 instance reboot failing, for example disk mounts failing due to mount point changes that were
not reflected into init scripts
 sshd killed by kernel out-of-memory reaper, failing to look into console output for diagnosis
 ... and many more
Some of these are from beginners failing to read the getting started guide, some are more
subtle and can happen even to veteran EC2 users. Then there are emails from Amazon saying
"we have noticed that one or more of your instances are running on a host degraded due to
hardware failure," and I wonder how many users don't get these emails because their AWS
account's email address points into a bit bucket.

No doubt there are real failures as well, where a host dies and takes the instances with it, or
one of the disks used by an instance gives up, which is the end of that instance. The question
here is how frequent this is relative to the total number of instances running, and since
Amazon is so secretive with its numbers it's difficult to make an educated guess. I tried to go
back into our year of logs to see whether I could estimate the failure rate, but I don't have
enough data to distinguish failure from shutdown.

The failures that concern me the most are actually not instance failures but network failures.
Anyone who has set up a large data center knows that network issues are the most difficult to
get under control. The damned network just keeps changing, and as soon as you try to hold
still your service providers change stuff. Some of the instance disappearances are really
network issues that cause an instance to be unreachable, or unreachable from certain other
instances. These are hard to troubleshoot, and on more than one occasion I've had to run
tcpdump on both ends to see packets departing and never arriving - if I can get to the target
instance at all to run tcpdump, that is. I hope Amazon gets a better handle onto this type of
failure and provides us with better troubleshooting tools. In the meantime, it's important to
flag issues to them so Amazon can troubleshoot and eliminate the root causes.

The really good news is that the Amazon folks are dedicated to figuring out what's going
wrong and fixing it. If you have an issue, do the troubleshooting you can, then set the
 instance aside, launch a new one to take its place, and post all the details on the forum. Shut
the instance down only after the issue is looked at. Looking back, there were two big issues
causing instance termination. One was the day when some EC2 front end explicitly
terminated a bunch of instances by error. Not good, but from what we saw it wasn't a massive
failure either. Amazon clearly has done its best to ensure this doesn't recur. The other was an
instance reboot bug that caused many instances to die in the reboot process. We learned not
to reboot ailing instances but instead to relaunch and rescue any data. This issue also seems to
be fixed at this point.

To summarize, if you can't reach an instance, here is what you should do:

 try to SSH, check the security group

 distinguish SSH timeout from key issues (timeout vs. permission denied errors)
 use ping to test connectivity (enable ICMP if you have the bad habit of disabling it)
 check the console output (use the convenient button on the RightScale dashboard); note that it
can take a few minutes for stuff to appear
 look at RightScale monitoring to see whether the instance is still sending monitoring data
 hop onto an instance in the same security group and try connecting from there (launch an
instance if you don't have any)
 post details (instance ID, what you've tried, symptoms observed) on the forum and set
instance aside
All in all, the number one lesson is "relaunch!" There are thousands of instances waiting to be
utilized, so use a fresh one if you see trouble with an existing one. If you master this step you
can use it in so many situations: to scale up, to scale down, to handle instance failure, to
handle software failure, to enable test setups. If you use RightScale, you will notice that that's
also what we focus on - making it easier to launch fresh instances.

Infrastructure:

IAAS (Infrastructure as a Service): IAAS (Infrastructure as a Service) is the base layer and
typically provide access to networking, virtual machines, storage. The client has the highest
level of flexibility and management over resources compared to PAAS and SAAS.
 Amazon Elastic Compute Cloud (EC2)

Amazon Global Physical Infrastructure

(Geographical Regions, Availability Zones, Edge Locations)

 It looks like Amazon would be losing a lot of money if not for AWS

Amazon reported its second-quarter earnings today, and it was a bit of a whiff — and a
bummer for Jeff Bezos, who is now no longer the solar system’s richest human and has been
relegated to the unfortunate position of second-richest human.

The company’s earnings came in lighter than Wall Street expected. But Amazon’s cloud server
farms, AWS, once again appear to be propping up Amazon’s profitability. The company’s huge
bet on building up the basis of modern cloud computing could, in a way, be held partially
responsible for Amazon’s long streak of profitability for the past many quarters.

Here’s a quick breakdown of that:

Amazon’s AWS Shines

Amazon has turned AWS into a business that’s on track to generate well over $10 billion in
revenue annually. It also has some of the best margins of all of Amazon’s lines of business, and
it continues to grow at a very healthy rate. AWS revenue was up 42 percent in the second
quarter compared to 2016. That growth is slowing a bit, as AWS revenue was up 58 percent
between 2015 an 2016.
Perhaps most importantly, Amazon signaled that it might return to losing money in the next
quarter. Amazon has long been known to burn cash in the quest to continue to grow into one of
the largest companies in the world, and Wall Street has generally been quite patient with that
strategy. Yet despite that, Amazon put together a string of strong quarters and profitability, and
on the year the company’s stock is up 40 percent.

It looks like that huge bet on building a bunch of buildings with servers inside is paying off as
Amazon continues to look into other lines of revenue. Amazon is well known to bulldoze its
way into new businesses, whether that’s buying a ton of grocery stores for $13.7 billion or
running a video streaming service for people playing video games. While AWS’s growth is
slowing, it certainly looks like it may be one of Amazon’s buoys for some time to come.

Reference

 https://cloudcomputingseminar.wordpress.com/2012/09/02/unit-xv-case-study-
amazon-ec2/
 https://techcrunch.com/2017/07/27/it-looks-like-amazon-would-be-losing-a-lot-of-
money-if-not-for-aws/
 https://www.rightscale.com/blog/cloud-management-best-practices/top-reasons-
amazon-ec2-instances-disappear
