Select Page

7 Steps: 1-3 Due Jan 8; 4-7 Due Jan 15Your next challenge is to create a cloud migration plan document while aligning it with BallotOnline’s latest IT policy. A successful cloud migration plan will encompass reviewing both the existing workloads and the post-migration state of the workloads. If the cloud migration plan is set up correctly, you and your migration team will be able to assess some important components, including how to move the existing workloads to the cloud, how to migrate data to the cloud, and any related API integration or automation. The executive board has made it clear that this Cloud Migration Plan should incorporate industry best practices and standards and meet the relevant business and technical needs of the organization.WILL PAY MORE IF EXTRA PAGES ARE NEEDED
instructions_project_1_final_cloud_migration_plan.docx

Unformatted Attachment Preview

Project 1: Final Cloud Migration Plan
Start Here
Your next challenge is to create a cloud migration plan
document while aligning it with BallotOnline’s latest IT policy.
Professionals in the Field
This short video features an IT professional describing the many
kinds of challenges he has faced when implementing a cloud
migration.
CCA640 Course Introduction
A successful cloud migration plan will encompass reviewing
both the existing workloads and the postmigration state of the
workloads. If the cloud migration plan is set up correctly, you
and your migration team will be able to assess some important
components, including how to move the existing workloads to
the cloud, how to migrate data to the cloud, and any related API
integration or automation.
The executive board has made it clear that this Cloud Migration
Plan should incorporate industry best practices and standards
and meet the relevant business and technical needs of the
organization.
Step 1: Research Cloud Premigration
Considerations
In this step, you will research premigration considerations, such
as the analysis of the current workloads that are being served
out of BallotOnline’s existing IT infrastructure, and how
the cloud migration plan will align with business objectives
and BallotOnline’s updated IT policies, which includes the cloud
addendum you recently wrote.
Take Note
Your supervisor, Sophia, has recommended that you use your
Cloud Adoption Policy Addendum: Cloud Infrastructure
Planning, Design, and Configurations, as you are looking at
migration considerations.
Cloud Adoption Policy Addendum
Your final report should be eight to 15 pages in length in either Microsoft Word or PDF format. The
report should contain the following headings:
1. Executive Summary (< 1 page) 2. Policy Scope (<1 page) a. Overview b. List of Approved "Cloud Ready" Applications 3. Alignment with Existing IT policies (<1 page) 4. Growth Projections Analysis (<1 page) 5. Service-Level Agreements in the Cloud (1–2 pages) 6. Data Security, Privacy, and Governance (2–3 pages) 7. Cloud Vendor Governance Strategy (1 page) 8. Business and Technical Impact (2–3 pages) 9. Exit Strategy (<1 page) 10. Resources and Escalation Contacts (<1 page) There are some factors to consider in understanding the technical and business impacts of any proposed workload migration plan. These include premigration assessment, data migration, application migration, API integration or automation, and user migrations. Step 2: Review and Compare Cloud Premigration Assessment Tools In this step, you will learn about some of the leading tools available that can aid in the cloud premigration assessment and help you identify the technical requirements for each workload to be migrated to the cloud. Take Note Your supervisor, Sophia, has asked you to review the following cloud premigration planning and assessment tools, and create a table that will compare each tool and highlight their capabilities: • AWS Application Discovery Service • NetApp OnCommand Insight After reviewing and creating the feature comparison table for the above-listed tools, using the Premigration Assessment Tool Comparison Template. Premigration Assessment Tool Comparison Template 1. Overview 2. AWS Application Discovery Services Overview 3. NetApp OnCommand Insight Overview 4. Comparison 5. Usability of Each Tool 6. Summary Submission for Project 1: Pre-Migration Assessment Tool Comparison Step 3: Explore AWS Application Discovery Service Premigration Terminology Application inventory: List of all the applications. Application dependencies and baseline system mapping: All the components that an application relies on for its optimal operations are referred to as its dependencies. Initial alignment of IT resources with the applications is referred to as baseline system mapping. Process performance: Process performance is the performance of each process that an application uses for its optimal operations. As part of the migration planning process, you may want to learn about the details with AWS Application Discovery Service before you deploy it to analyze BallotOnline’s workloads later in the migration planning process. AWS Application Discovery Service uses either agents or collectors to discover the performance, capacity, and applications running on individual as well as multiple systems/servers. The service collects and presents configuration, usage, and behavior data from your servers to help plan migration projects, allowing you to identify application inventory and application dependencies, establish and map a baseline for your system, and determine process performance. STEPS 1-3 DUE JANUARY 8 Step 4: Install AWS Application Discovery Agent https://console.aws.amazon.com/iam/home?#/users$new?step=details&accessKey&login&userNames= CCA640HyperVMigration&passwordType=autogen&permissionType=policies&policies=arn:aws:iam::aw s:policy%2FServerMigrationConnector&policies=arn:aws:iam::aws:policy%2Fservicerole%2FServerMigrationServiceRole jwhite161@student.umuc.edu umuc161! At this point in the migration planning process, you’ve considered premigration issues, reviewed premigration assessment tools, and familiarized yourself with AWS Application Discovery Services. You are now ready to install AWS Application Discovery Agent. Application Discovery Agent is important because it will allow you to collect information from the server about the performance, capacity, and application on a specific server. This information will be helpful with sizing the target AWS service for this workload. Action Item Note that before you can install the AWS application, you need to create an environment for the application by setting up a web service stack, known as a LAMP stack, using the LAMP Stack Deployment Guide. Deploying a LAMP Stack in AWS Use the following procedure to create and deploy a LAMP stack in AWS. To deploy a LAMP stack: 1. Open the Amazon CloudFormation Service In the upper left corner, choose Create Stack. Used with permission from Amazon Web Services. Now, in the middle of the screen, go to Select a sample template from the drop-down menu. Used with permission from Amazon Web Services. Under Single Instance Sample, select the LAMP Stack template and click Next. Under Specify Details, add the following details to the template: Parameter Stack name DBName DBPassword DBUser Instance Type KeyName SSHLocation Input CCA640LAMPStack cca640 cca640 cca640 Default as t2.small Use any existing key pair or create a new EC2 key pair Default as 0.0.0.0/0 Used with permission from Amazon Web Services. Now, click Next. Used with permission from Amazon Web Services. Keep the user defaults the same and click Next. Used with permission from Amazon Web Services. Now, click Create to finalize the creation of the LAMP stack. Used with permission from Amazon Web Services. Lab completed. This LAMP stack will be configured to be similar to an existing server that BallotOnline has in production. You will then install the AWS Application Discovery Agent https://docs.aws.amazon.com/application- discovery/latest/userguide/what-is-appdiscovery.html on your LAMP stack server. As a proof of concept, test the AWS Application Discovery Agent in a test environment. Remember, you should always perform a test prior to implementing anything new in a production environment. Action Item Use the following resource to install AWS Application Discovery Agent: • • Discovery Agent installation steps https://docs.aws.amazon.com/application-discovery/latest/userguide/discoveryagent.html#install_on_linux Step 5: Start Collecting Agent Data In the previous step, you installed AWS Application Discovery Agent. It’s now time to perform a discovery of the LAMP stack, which gathers information about all the processes running in the server, system performance, and network connection information. This is needed prior to the migration. AWS Application Discovery Agent provides a set of public API (application programming interface) operations and open data formats. These allow the program to work with other tools. Action Item Go to the Start Discovery Agent Data Collection https://docs.aws.amazon.com/application-discovery/latest/userguide/discoveryagent.html#start-agent-data-collection for guidance how to start collecting server data. After you have deployed AWS Application Discovery Agent, proceed to the next step, where you will evaluate the data you collected. Step 6: Evaluate the Data Collected In this step, you will evaluate the results of the discovery conducted in the previous step. After analyzing the results, you will be in a better position to appropriately plan the migration of the workload to AWS. Action Item Export and download the data collected by AWS Application Discovery Agent and analyze the data to identify application processes running on the server, view the application dependencies, map a baseline for your system, and determine process performance. See View, Export, and Explore Discovered Data for guidance. https://docs.aws.amazon.com/application-discovery/latest/userguide/view-and-export.html Make sure that you specify the export start date/time of less than 72 hours before the current date/time. Review performance data and processes to identify dependencies. Based on your analysis, provide recommendations and your rationale for the most appropriate AWS service for the migration. Key Points Keep in mind that your LAMP server is not running any additional applications, so its load is not heavy. But you will see what data is collected so you can come to a conclusion about the usability of AWS Application Discovery. On a production server, the data will be more reflective of the server’s application load and its performance. Submit a draft summary of your evaluation findings in the dropbox below to get feedback. Step 7: Write the Final Cloud Migration Plan Now you can consolidate the work that you have completed in the steps along with some additional elements (scope, executive summary, etc.) to create a comprehensive migration plan that aligns to BallotOnline’s existing IT policies. Sophia will present your work for approval at the executive meeting. Professionals in the Field At this point, you should have a better understanding of the cloud migration strategy and how a cloud migration plan differs from a traditional IT data center migration plan. This knowledge differentiates you from a traditional IT professional and solidifies your standing in the ranks of cloud computing professionals. The final document should be between eight and 10 pages. Use the Cloud Migration Plan Template to write your Cloud Migration Plan. Cloud Migration Plan 1. 2. Executive Summary (< 1 page) Scope (<1 page) a. b. 3. 4. Cloud Premigration Considerations (<1 page) Cloud Migration Planning Assessment Tools (1–2 pages) a. b. 5. Overview (<1 page) Cloud Migration prerequisites Feature Comparison Evaluation Summary AWS Application Discovery Services (1–2 pages) a. b. 6. 7. 8. Agent-Based Option Agentless Option Evaluation of Discovered Application and Infrastructure Data (1–2 pages) Migration Recommendations (2–3 pages) Conclusion (<1 page) Before you submit your assignment, review the competencies below, which your instructor will use to evaluate your work. A good practice would be to use each competency as a self-check to confirm you have incorporated all of them in your work. • 9.1: Develop a plan for cloud implementation / migration. • 9.3: Develop documentation (plans, policies, and procedures) to support a cloud operation. • 10.3: Configure cloud management tools and software. • 10.7: Configure a public cloud infrastructure using industry leading provider(s). • 11.1: Perform system auditing. • 11.3: Upgrade the infrastructure to increase capacity. • 11.4: Monitor system performance. • 11.5: Perform system maintenance. STEPS 4-7 DUE JANUARY 15 ... Purchase answer to see full attachment