Cloud Migration: Final Proposal and Presentation

profilecnjoku642
Week_5_Assignment-1.docx

Running head: MARKETING PLAN PROPOSAL 1

MARKETING PLAN PROPOSAL 4

Marketing Plan Proposal

CHIDI NJOKU

NTC/302

06/01/2020

Matt Mancani

Marketing Plan Proposal

Moving to cloud is a big market change that can make any organization increase its overall sales and revenues. Being that profit gains are the most important aspects of the business; owners continuously look at ways to cut costs. Cloud storage is a reasonable route because suppliers assume the expenses of the framework and administration saving the company’s money. The expense of hardware and maintenance cost are significantly reduced when migrating to the Cloud. With the use of off-site server farms and software (the cloud) companies can save thousands of dollars in maintenance and personnel salaries.  

The four types of cloud migration are called lift and shift, shift to Software-as-a-Service (SaaS), application refactoring, and replant forming. Lift and shift provide the same software that your company used in the data center, but now in the Cloud. This is the fastest method for migrating applications to the Cloud and the one that causes the least disruption. It only requires the involvement of the infrastructure and security teams. It's also the option with the least upfront cost. Moving the application to the Cloud allows it to handle peak performance, without your company having to pay for it. The process of shifting to SaaS means outsourcing one or more applications to a cloud service company that specializes in managing those applications. Companies do this on a request by application basis and only shift the applications they need to. Static applications can remain on-premises. Moving to SaaS frees employees up to focus on core competencies and the things that make a business unique and competitive. Outsourcing applications to SaaS also means that you need fewer licenses for business tools. However, it's essential when shifting an application to SaaS that you pick the right service. Refactoring is about prioritization; it provides lots of opportunities to save over time by minimizing spending on things you won't need once you're in the Cloud. You can save money on the platform itself as well by switching to cloud-native services that cost less than the ones you use on-premises.   

Refactoring isn’t just about cutting costs. It also allows you to make changes to your enterprise very quickly, which means that you can keep up with your customers. Refactoring lets you respond faster and prioritize updates (Shadow-Soft, 2017).

Cost

The principal profit, and maybe most paramount in the personalities of numerous entrepreneurs, is its cost advantage. Cloud storage is by and large more reasonable because suppliers appropriate the expenses of their framework and administrations crosswise over numerous organizations. The expense of hardware and maintenance are disposed of when it moves to the cloud. Evacuating these capital uses and the related administration pay rates from the engineering cost can decipher into noteworthy expense investment funds.

Costs.

Database 1

Hourly ($0.136)

3 Year cost ($7168)

Database 2

Hourly ($0.136)

3 Year cost ($7168)

Storage (10TB)

Monthly ($230 + Initial Fees)

3 Year cost ($9316.45)

Total

Monthly ($327.90

3 Year cost ($23652.45)

Security and Reliability

As opposed to having hardware inside the office, cloud storage is housed in a server farm, giving excellent security. Additionally, in the cloud, information is moved down to numerous servers, so if one server crashes, the information is protected and is put away in different areas. The potential hardware breakdown danger gets to be insignificant when information is securely put away in excess areas.

A drawback of the cloud is that if your internet connection is down, you will lose access to the cloud service. A healthy alternative that can satisfy this is to use on-site servers instead. On-site or local servers are easily and readily accessible and can be quickly backed- up to a networked device. They're typically more secure too, as everything is managed from one location.

Preliminary Plan

We could start with getting server equipment for the main office and migrating data to the new servers. A maintenance plan for security and upkeep of the servers can be put in place as well. Then we can start to get hosting for our data over the cloud. Access can be setup so that certain levels and certain personnel can continue to be productive in a mobile nature.

All in all, moving to the cloud is a great idea for future growth. The cost is minimal and a lot of features are one time purchases that ensure future success. All the concerns of the company and be met so that data loss can be minimal or non-existent. This move will create a surge in productivity by effectively using technology.

Migration

AWS (high-level diagram)

Matrix

The current structure consists of an ecommerce system that is set to allow access to various users. The three user types are; Customer, Administrator and system. The matrix uses the term user to represent the system to system access. These three access levels have been aligned to operate in one broad system. Each user in the AWS transactional system has restrictions and limits (Amazon Web Services 2020). For instance, the customer can only access the region and details that involves customers. On the other hand, the admin has the mandate to access all the sections. However, the admin is restricted to access personal client information. Since each user has specific privileges, the rate of accessing the system, is also different. These restrictions are put in place to enhance the security as well as ensure the end to end exchange of data is up to data and confidential.

The security benefits of the current system involve having a robust system that cannot be accessed by a third party. Through the database, the system has been strengthened by the use of matrix that allows each user to access the specific locations of the system. The system also has encryption techniques that allow it to be unique and robust (Mukherjee, 2019). The staff has the mandate to use the system without facing interruptions or lose of data to third parties. Moreover, through the system, unlimited server capacity is maintained each time a user is accessing the system. The system is also flexible to use and can easily accommodate a new user. In addition, the structure and model of the program makes it to have an ease of usage for both customers and staff.

References

Amazon Web Services (2020). AWS Security Best Practices. Retrieved from: https://d1.awsstatic.com/whitepapers/Security/AWS_Security_Best_Practices.pdf

Banerjee, J. (2018). AWS certified solutions architect associate all-in-one exam guide. New York, NY: McGraw-Hill Education.

Hu, W., Si, J., & Li, H. (2018). Security-Reliability Tradeoff Analysis in Multisource Multirelay Cooperative Networks with Multiple Cochannel Interferers. Wireless Communications & Mobile Computing, 1–12. https://doi.org/10.1155/2018/2379427

Jasgur, C. (2019). Leveraging disaster recovery in the cloud as a cloud migration path: A case study. Journal of Business Continuity & Emergency Planning, 13(2), 150–159.

Mukherjee, S. (2019). Benefits of AWS in Modern Cloud. Available at SSRN 3415956.

Shadow-Soft, (2017). Retrieved from: https://shadow-soft.com/cloud-migration-models/