The Ericson Cloud System Case Study

The Ericson Cloud System includes the Ericson Cloud Execution Environment, which is based on Opponents Cloud Management and KAVA hypertensive (Ericson defines the cloud evolution, 2013). The solution is an addition to the existing ASS system, the Ericson Cloud Manager.

It offers a smooth migration as it builds on the Ericson Blade System and Ericson USSR and it allows brutalized and non-brutalized applications to execute side-by-side with maintained carrier-grade performance.

We Will Write a Custom Case Study Specifically
For You For Only $13.90/page!

order now

The system provides an execution environment for applications irrespective of the source – whether it’s Ericson, the operator, a partner or other innovators. This makes it possible to introduce new services and consolidate existing ones onto the same brutalized platform (Ericson defines the cloud evolution, 2013) Ericson uses Amazon Elastic Compute Cloud (Amazon ICE), Amazon Simple Storage Service (Amazon SO), and Architects for provisioning and auto-scale functionality. Hey host in multiple SAWS locations with failover between installations, partly based on Architects features. Ericson explains that its solution was built primarily using laves, and hosted on Tomcat and Myself, using Happily for load balancing (SAWS Case Study: Ericson, 2013 ; Ericson defines the cloud evolution, 2013) The many chose Amazon Web Services (SAWS) because they felt SAWS was the most Integrated public cloud provider in the Architects Cloud Management Platform Bagatelle).

The Ericson team states that having hosting centers in various regions Nas important for them. SAWS also showed a better quality of service with solid management and a proven track record (SAWS Case Study: Ericson, 2013). Ericson benefited from Amazon Web Services (SAWS) through cost reductions, automated software updates, and remote access capabilities enhanced by on-demand availability supporting multiple devices.

Amazon Web Services (SAWS) is a self-service environment accessible at all times and available with full access without any contracts or long term subscriptions, thus making SAWS an affordable global infrastructure (Amazon Web Services, 2013) The Ericson team explains that it has several Software-as-a-Service (AAAS) initiatives that have or will soon need an Infrastructure-as-a-Service (alas) provider, such as SAWS, and that the current SAWS solution being used is attracting a lot of attention within the company because of its advanced automation and global hosting (SAWS Case Study: Ericson, 2013).

Amazon Nub Services (SAWS) delivers a highly scalable cloud computing platform with high availability and reliability, and the flexibility to enable customers to build a wide range tot applications.

In order to provide end-to-end security and end-to-end privacy, SAWS builds services in accordance with security best practices, provides appropriate security features in those services, and documents how to use those features.

In addition, SAWS customers must use those features and best practices to architect an appropriately secure application environment. Enabling customers to ensure the confidentiality, integrity, and availability of their data is of the utmost importance to SAWS, as is maintaining trust and confidence (Amazon Web Services, “What is cloud computing? “2013). With Ericson utilizing each of the different services within the SAWS, they are too secure.

SAWS cloud is architect to be secure and contains a number of capabilities that restrict unauthorized access or usage without sacrificing the flexibility that customers demand. SAWS enables users to encrypt their personal or business data within the SAWS cloud and publishes backup and redundancy procedures for services so that customers can gain greater understanding of how heir data flows throughout SAWS, this decreases the potential for Ericson and its consumers using the cloud to be at risk (Amazon Web Services, Security, 2013).