Cloud Computing: Ericson Merge With Aws

Cloud Computing: Ericson Merger With Aws

Cloud Computing: Ericson Merging With Aws

Cloud Computing: Ericson Merge with AWS

Cloud Computing: Ericson Merge with AWS

Improvising cloud computing on high-end telecommunication technologies is reliable and advisable since this feature attracts manageability, scalability, and adaptability of the network. Cloud computing ensures that networks are configured to meet reliable standards, and this is profitable since the improvising company can manage its technology onsite without disturbing the client systems. A good example is Ericsson's collaboration with Amazon Web Services (AWS) in improvising remote cloud computing for different clients globally. The research will examine this partnership and prove that remote cloud computing is decisive approach to respond to future challenges.

How Ericsson benefited from Amazon Web Services (AWS)

Ericson's objective was centered in improvising right scale cloud management platform to manage networks. The goal was to have distributed service system and enable agility. This was vital since subscriber's support could have been distributed enabling efficiency. Ericson benefitted from Amazon web services since this company offered multiple technologies geared towards improvising a reliable choice in cloud computing. The goal enabled multiple subscribers to dock on remote servers and this ease agility of networks (AWS Case Study: Ericsson, 2014).

For the above reasons, Ericson was capable of the reaching over 2 billion subscribers' worldwide using AWS platforms. Through some of the ideal products like Amazon Elastic Compute Cloud (Amazon EC2), and Amazon Simple Storage Service (Amazon s3), Ericson was capable of achieving Right scale for auto-scale functionalities. Devi (2012, pp. 19) suggests that cost was mitigated through the increased number of subscribers and improvising of multiple AWS location, which have failover between installations and right scale features. In addition, remote AWS locations were easily updated, remotely assessed and available by field engineers, and this reduces the cost of back-ups and reconfiguration of the entire system, which was time and cost ineffective.

Evaluate the scalability, dependability, manageability, and adaptability of AWS

AWS platforms provide effectively for Ericson technologies. The underlying feature was combining computing, storage, and networking resources to allow consumers to utilize services globally. AWS platform were dependable since they enabled storage of mass data with optimal security and easy of accessibility. Secondly, AWS platform were scalable since servers could be managed remotely. On-site field technician could upload and modify configuration files without disturbing other units. Thirdly, AWS platform enabled Ericson adaptable to various network (Kim and Bahn, 2013, pp. 6).

Currently, Ericson offers support service to multiple telecommunication companies. Technologies offered include; 2G, 3G and bloated 4G. Most of these subscribers are located in different networks at different jurisdictions. Therefore, teaming up with Amazon enables the deployment of Amazon Elastic cloud. Ericson close examines whether deployment will adapt to the required standards. Hence, teaming up with AWS enables the utilization of Amazon Simple Storage services. Lastly, AWS platforms enabled the effective management of the networks and servers. Technicians running the JavaSE, which was hosted on Tomcat and MySQL, using HAProxy could configure the servers, upload new code updates, and review bugs of each network based on the client's expectations (Kim and Bahn, 2013, pp. 6). This was easy and decisive because the client would receive customized frameworks for their products.

Security Concerns

From the mentioned principles, it is essential to note that AWS improvised a higher degree of security since it was manageable and reliable. However, security was not optimal, and there were issues, which had to be addressed. Ericson privacy policy and service agreement do not meet proper requirements of a secure network. Malicious attacks through viruses and horses could be instigated from the inside and outside. The problem is that client deploys his own background software and infrastructure, and this could be prone to attacks on aggregate.