+1443 776-2705 panelessays@gmail.com

This report will provide a comprehensive cloud migration approach and tool sets that align with BallotOnline’s technical and business requirements. The final document should be between eight and 10 pages.

Cloud Migration Technical Report Template

· Executive Summary (< 1 page)

· Plan Scope (1 page)

· Overview

· Cloud migration prerequisites

· Industry Leading Cloud Migration Approaches Overview (<1 page)

· Cloud Migration Tool Sets (1-2 pages)

· Feature Comparison

· Evaluation Summary

· AWS Database Migration Service (1-2 pages)

· Overview

· Prerequisites

· Data Migration of MySQL Database to AWS (1-2 pages)

· Private Cloud (Hyper-V) Migration to AWS (1-2 pages)

· Cloud Migration Recommendations (1 pages)

· Conclusion (<1 page)



Project 3: Perform Migration

Step 1: Research Industry Standard Data Migration Approaches

Step 2: Review and Compare Data Migration Tool Sets 

Review the two toolsets: 


AWS Server Migration Service


 and 


AWS Database Migration Services


, and compare them in the 


Cloud Data Migration Tool Sets Comparison Template


.

Step 3: Explore and Evaluate AWS Database Migration Service 

Step 4: Review Options for Database Migration to AWS

Review the following three 


options for database migration to AWS


:

· Migrating from an RDS MySQL database instance to AWS

· Migrating from a MySQL database external to Amazon RDS to AWS

· Migrating from a database that is not MySQL-compatible to AWS

Step 5: Migrate Data from a MySQL Database to AWS

Now that you have finished researching approaches, tool sets, and options, you can start the migration process. In this step, you will migrate BallotOnline’s human resources data from the external MySQL database to an 


Amazon Aurora MySQL


database.

Step 6: Perform Private Hyper-V Cloud Migration to AWS

Follow the 


Private Cloud Migration Lab Guide


 for detailed instructions on how to perform the private cloud migration to AWS using Server Migration Service (SMS).

The basic steps are:

1. Create a role for the migration and name it SMS. This role will be used in the next step.

2. Create and complete the replication job in Server Migration Service. This step will create an AMI (Amazon Machine Image) off the migrated server.

3. Deploy an EC2 instance using the AMI from Step 3 above to verify the migration.

Take screenshots for each step since they will be be used in your final Cloud Migration Technical Report.

Don’t forget to clean up the AWS resources to avoid any charges.

Step 7: Write the Final Cloud Deployment Programmatic Approach Document

Now that you have migrated both databases, your Cloud Migration Technical Report will consolidate the work that you have completed in the steps along with some additional elements (scope, executive summary, etc.).

This report will provide BallotOnline with a comprehensive cloud migration approach and tool sets that align with BallotOnline’s technical and business requirements. The final document should be between eight and 10 pages. Sophia will present your work for approval at the executive meeting.

Submit your work via the dropbox below using the 


Cloud Migration Technical Report Template


.