Case Study 2 Cloud Computing

Topics: Cloud computing, Amazon Web Services, Pages: 7 (1391 words) Published: March 7, 2015

Case Study 2: Cloud Computing
Bradley Wallace
Strayer University
Professor Mark Cohen
November 30, 2014


Over a span of several years, has progressively positioned itself as a competitive technology company through a series of services referred to as Amazon Web Services (AWS). These are services in which Amazon rents out parts of its back-end infrastructure to other IT organizations and developers (New York Times, 2010) since 90% of it was being unused. They offer a number of benefits such as cost-effectiveness, dependability, flexibility, and comprehension. The competitive AWS products in which Amazon emphasized were Mechanical Turk, Simple Storage Service (S3) and Elastic Compute Cloud (EC2).   Ericsson was able to instantly take advantage of Amazon’s resources. Amazon’s AWS is able to build and manage a global infrastructure to the scale Ericsson needed to support their business. This infrastructure already brings Cost-effectiveness to Ericsson due to “No up-front payments, No long-term contracts. Customers pay only for actual usage of services with help of their credit card (Pay as you go).” They had the ability to deploy new applications and automated software updates instantly because they were able to scale up and down as demand changed or the business required it. They could access their cloud from anywhere thanks to the freedom of remote access. It can supply millions of transactions per minute. A lot of commodity hardware that can pick up in case of some technical failures on the other hardware. (Always-on and self-healing infrastructure) The web services provided Ericsson with a highly reliable, scalable, low-cost infrastructure platform with data center locations in the U.S., Europe, Singapore, and Japan. “The Ericsson team states that having hosting centers in various regions was important for them. AWS also showed a better quality of service with solid management and a proven track record.” (Amazon Web Services, 2012) Amazon Elastic Compute Cloud (Amazon EC2) provides a complete environment, a processor, memory, and preconfigured software. It reduces the time need to obtain and boot new server in a significant high speed. As a result, customers are allowed to quickly scale capacity, both up and down, as your computing requirements change. With Amazon EC2, customer will be benefitted from policy that pays only for using capacity in real time. Amazon EC2 provides developers the tools to build failure resilient applications and isolate themselves from common failure scenarios. (Amazon Web Services, 2012) Amazon S3 is simply storage for the Internet. Its design helps developers easily to access Web-scale computing. It is easily used to store and retrieve any amount of data, at any time, from anywhere on the Internet thanks to a simple Web services interface. Any developer can access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of Web sites. The service aims to maximize benefits of scale and to pass those benefits on to developers. Amazon S3 is so flexible that protocol or functional layers can easily be added. Reliability is backed with the Amazon S3 Service Level Agreement. As with most cloud services, you pay for what you use. (Amazon Web Services, 2012) Rightscale is considered as a bridge between your applications and your cloud infrastructure. Rightscale cloud management enables organizations to easily accomplish and manage business-critical applications across public, private, and hybrid clouds. Right Scale provides efficient configuration, monitoring, automation, and governance of cloud computing infrastructure and applications. (Crunch Base, 2012) One of its features enables the user to monitor, scale, and manage entire server deployments efficiently and reliably. (Rightscale Cloud Management, 2012). It offers the freedom and flexibility to keep...

References: Amazon Web Services (2012) About AWS. Retrieved from
Business Day. (2013, May 18).   New York Times. Retrieved from:
Chantry, D. (2009) Mapping Applications to the Cloud. Retrieved from:
Crunch Base (2012). Retrieved from:
Gottlieb, A. (2011) Cloud Computing Journal: Beware the Network Cost Gotchas of Cloud
Computing. Retrieved from:
Rightscale Cloud Management (2012) A Bridge between Your Apps and Infrastructure.
Retrieved from:
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Cloud Computing Essay
  • Cloud Computing Essay
  • Cloud Computing Essay
  • cloud computing Essay
  • Cloud Computing Essay
  • Amazon Case Study 2 Essay
  • Essay about Tesla Case study 2
  • Cloud Computing Unit 2 Lab 1 Essay

Become a StudyMode Member

Sign Up - It's Free