Computer Science
UMUC Cloud Postmigration Postmigration Activities with AWS Lab Report

University of Maryland Global Campus

Question Description

I don’t understand this Computer Science question and need help to study.

Now that you have completed BallotOnline's Cloud Migration Technical Report, you have a better understanding of the available cloud migration approaches and options, and how these approaches differ from traditional IT deployment approaches. It's now time to get the migrated workloads in a production-ready state, and as the cloud architect, you need to come up with a postmigration plan and related activities.

You know that it is important to plan for postmigration activities because after the data and applications are migrated, they need to be validated and tested to ensure a positive user experience and an acceptable application services delivery after the move to the cloud.

To do that, you will evaluate and compare different postmigration activities and approaches, and choose the best approach for BallotOnline, along with your rationale for selecting the specific approach or activity. You will compile this into a Cloud Postmigration Activity Report for the staff and leadership at BallotOnline.

Your supervisor, Sophia, has continued to stress that the postmigration activities must incorporate industry best practices and standards and meet the relevant business and technical needs of the organization.

There are seven steps to complete this project

Take Note

This project has a hands-on lab. Instructions for the lab are included in the steps of this project.

Competencies

Your work will be evaluated using the competencies listed below.

9.1: Develop a plan for cloud implementation / migration.

9.5: Design a virtualized network infrastructure to meet business needs.

9.6: Design cloud storage infrastructure to meet business needs.

10.2: Create and deploy virtual machines.

10.3: Configure cloud management tools and software.

10.4: Configure cloud orchestration and automation software.

10.7: Configure a public cloud infrastructure using industry leading provider(s).

11.1: Perform system auditing.

11.5: Perform system maintenance.

11.6: Troubleshoot system problems.

11.8: Prepare contingency plans when changing cloud providers or closing down a cloud architecture.

Unformatted Attachment Preview

Project 4: Postmigration Activities Start Here Now that you have completed BallotOnline's Cloud Migration Technical Report, you have a better understanding of the available cloud migration approaches and options, and how these approaches differ from traditional IT deployment approaches. It's now time to get the migrated workloads in a production-ready state, and as the cloud architect, you need to come up with a postmigration plan and related activities. You know that it is important to plan for postmigration activities because after the data and applications are migrated, they need to be validated and tested to ensure a positive user experience and an acceptable application services delivery after the move to the cloud. To do that, you will evaluate and compare different postmigration activities and approaches, and choose the best approach for BallotOnline, along with your rationale for selecting the specific approach or activity. You will compile this into a Cloud Postmigration Activity Report for the staff and leadership at BallotOnline. Your supervisor, Sophia, has continued to stress that the postmigration activities must incorporate industry best practices and standards and meet the relevant business and technical needs of the organization. There are seven steps to complete this project Take Note This project has a hands-on lab. Instructions for the lab are included in the steps of this project. Competencies Your work will be evaluated using the competencies listed below. 9.1: Develop a plan for cloud implementation / migration. 9.5: Design a virtualized network infrastructure to meet business needs. 9.6: Design cloud storage infrastructure to meet business needs. 10.2: Create and deploy virtual machines. 10.3: Configure cloud management tools and software. 10.4: Configure cloud orchestration and automation software. 10.7: Configure a public cloud infrastructure using industry leading provider(s). 11.1: Perform system auditing. 11.5: Perform system maintenance. 11.6: Troubleshoot system problems. 11.8: Prepare contingency plans when changing cloud providers or closing down a cloud architecture. Step 1: Postmigration Activities Overview Like any software development project, migration projects require careful planning to ensure success. This planning includes the postmigration testing and maintenance phase. Start this project by researching and planning the postmigration activities that will be required to get BallotOnline's migrated workloads in a production-ready state. Postmigration Strategies After the migration to the cloud takes place, the focus shifts to maintaining performance and correcting possible complications. The migration efforts must be sustained over the long term to retain the benefits gained while exploring ways to use the elasticity and scalability of the cloud. Examples of the kinds of questions you may consider when planning a postmigration strategy include: Standards and Controls • • Have we established standards for completeness, reliability, accuracy, timeliness, customer satisfaction, quality, and cost? Are controls in place and consistently applied? Monitoring and Management • • • • • • • Data-driven insights on performance will help you make decisions. Is a comprehensive monitoring strategy in place? Numerous tools are available to provide application-level insights and monitoring on AWS. Are you taking advantage of cloud-native monitoring tools? Are you taking advantage of the resources provided in your cloud service provider's enterprise support package for technical information and guidance? Are pertinent alerts monitored, analyzed, and distributed to appropriate personnel? Are we appropriately measuring and monitoring risk? How do we we check that the migration project is implemented as planned, and assess how well it is working? Does performance meet all the customer's requirements? Performance Improvement • • • What elements (such as evaluation, organizational learning, and innovation processes) will be included in the cloud migration performance improvement system? Do our plans and policies allow you to take advantage of opportunities for innovation while maintaining security? How can we monitor the cloud migration decisions made and fine-tune them as they evolve? References Blokdyk, G. (2018). Cloud migration complete self-assessment guide. Retrieved from https://www.scribd.com/book/368507385/Cloud-Migration-Complete-Self-Assessment-Guide Orban, S. (2016). 21 best practices for your cloud migration. Retrieved from https://medium.com/aws-enterprise-collection/21-best-practices-for-your-cloud-migratione406546cb66b Step 2: Explore AWS CloudFormation AWS CloudFormation is a service which enables defining components of cloud infrastructure in the form of templates, which are text files written according to predefined syntax rules. Templates allow for automated creation of infrastructure configurations without human intervention. CloudFormation CloudFormation is one of the major services underpinning AWS's infrastructure as code capabilities and is crucial in enabling repeatable and consistent deployments of infrastructure. It allows you to manage sets of resources from other AWS services grouped into stacks and define these stacks in a template using JSON or YAML. The service itself is free, but you will pay for the use of related underlying resources. References CloudFormation is adapted from CloudFormation Basics from AWS-Guide, available under a Creative Commons Attribution-ShareAlike 4.0 International license. © openguides/og-aws and its contributors. Explore CloudFormation (https://aws.amazon.com/cloudformation/) and its templates, and Browse templates provided by AWS.( https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-sampletemplates.html) Action Item Follow the AWS guide Follow the AWS guide (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/working-withtemplates-cfn-designer-walkthrough-createbasicwebserver.html) to implement a template describing a simple web server environment configuration, and create a stack prescribed by the template you’ve created. Take screenshots of your template in the CloudFormation designer and of the deployed stack in the CloudFormation dashboard, and save them for the final Project 4 submission. Be sure to follow the guide directions carefully, making sure that resources are connected in the canvas exactly according to the guide, and parameters, mappings, and outputs are pasted into the correct places in the integrated editor. In the next step, you will compare the options for monitoring and management of your cloud files. Step 3: Compare Monitoring/Management Options in AWS Now that you have explored CloudFormation, you will consider resource optimization. Controlling and optimizing the infrastructure can help BallotOnline reduce costs, improve security, and increase performance. The monitoring and management options and tools will help automate IT operations for BallotOnline in the cloud. You've been asked to review two of the leading monitoring and management options available in AWS: AWS Trusted Advisor and AWS Systems Manager. After your discussion, compare the two options using the Cloud Monitoring and Management Comparison Template and submit it via the dropbox below. Cloud Monitoring and Management Comparison Review and compare AWS Trusted Advisor [external link: https://aws.amazon.com/premiumsupport/trustedadvisor/] and AWS System Manager. [external link: https://aws.amazon.com/systems-manager/] using the template below. The total length of your findings should be about two pages. Overview AWS Trusted Advisor Overview AWS System Manager Overview Comparison Usability of Each Toolset Summary of Features, Uses, Lessons Learned for Each Tool Step 4: Evaluate and Configure AWS Trusted Advisor In the previous step, you compared two maintenance and management tools, AWS Systems Manager and AWS Trusted Advisor, to gain an understanding of the capabilities of both resources. Sophia has asked you to get started by evaluating and configuring AWS Trusted Advisor next. Action Item Explore AWS Trusted Advisor and then go to the Trusted Advisor dashboard and check each category with best practices: 1. Cost optimization 2. Fault tolerance 3. Services limits 4. Security 5. Performance Recommend changes to the settings based on the results of the checks and document the results of each check with screenshots. Once you've evaluated and configured AWS Trusted Advisor, you can proceed to the next step, where you will do the same for AWS Systems Manager. Step 5: Evaluate and Configure AWS Systems Manager Now that you've finished the evaluation and configuration of AWS Trusted Advisor, you can set up AWS Systems Manager (https://aws.amazon.com/systems-manager/) to execute simple automation workflows for BallotOnline. Action Item Use the AWS Automation Quickstarts guide (https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-walksecurity.html) and follow steps in the Configuring Access to Systems Manager guide to configure AWS Systems Manager access and create a managed virtual server instance. Then, configure the following use cases, while taking screenshots to document your work: • Run an Automation Workflow as the Current Authenticated User https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-walk-securityuser.html • Run an Automation Workflow by Using an IAM Service Role https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-walk-securityassume.html Action Item Next, follow the steps listed in the guides linked below to create and configure State Manager associations by using the AWS CLI and automatically perform common administrative tasks. Don't forget to take screenshots to document your work. • Automatically Update SSM Agent (CLI) (https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-state-cli.html) Note: You can also create State Manager associations in the Amazon EC2 console (see Create an Association (Console)). Once you have evaluated and configured AWS Systems Manager, you can proceed to the next step to consider cutover/rollback options should a workload need to be returned to its original source. Step 6: Discuss and Review Final Cutover/Rollback Options You've evaluated and configured AWS Systems Manager and AWS Trusted Advisor. Now, it's time to consider plans in case something goes awry and data becomes unavailable when the project goes live. In this step, you will discuss and review final cutover strategy and options to roll back the workloads to the original source in an event of any postmigration issues. You will include your cutover options and rollback plan as part of your final Cloud Migration Technical Report. Cutover Strategy Cutover strategy refers to the process from moving from the old system to the new live environment. Such a strategy will include action start and end dates for the transition, along with checkpoints including a decision on whether to implement a rollback (Kalamaina, 2016). A cutover plan should include a checklist of everything that needs to occur when data is transferred. This might include, for example, putting a stop on the data coming in and going out, as well as informing users to stay out of the system during the cutover (Iyer, 2014). It should also include who is responsible for each activity. So the plan needs to include preliminary activities, including how to inform stakeholders—internal and external—before, during, and after the migration. The plan should also include a list of tasks to activate during the transfer, and should include potential time frames for each so that employees are aware. And of course, the plan should include the details for testing the system after the transfer, along with timelines. This section should also include when the system users can get back in (Iyer, 2014). A communication plan for employees and users of the system should also be part of the cutover plan. Such a plan would allow stakeholders/users an idea of when the system will go down, when it will be back live, and whom to contact throughout the cutover (Iyer, 2014). Checkpoints should be created for system monitoring during and after the migration. Finally, the cutover strategy should also provide details on a rollback procedure if it is necessary to restore the system to its original parameters. This should include the organization's backup strategies and options in case applications and/or integrations fail in the new system. References Iyer, S. (2014). Managing project cutovers effectively. Retrieved from https://www.mcftech.com/managing-project-cutoverseffectively/ Kalamaina, J. (2016). SAP project management pitfalls: How to avoid the most common pitfalls of an SAP solution . New York, NY: Apress. When you are finished, it's time for the final step, the rep Step 7: Write Cloud Postmigration Activity Report At this point, you should have a better understanding of the cloud postmigration activities and the services that are available to manage and monitor cloud infrastructure in AWS. In your Postmigration Activity Report, you will provide BallotOnline with postmigration activities options and tool sets that align with BallotOnline's technical and business requirements. The 10- to 12-page final document will consolidate the work that you have completed in the steps along with some additional elements (scope, executive summary, etc.) to create a comprehensive postmigration activity report. Use the Cloud Postmigration Report Template to make sure that you have included all the elements. Cloud Postmigration Report Template ● ● ● ● ● ● ● ● ● Executive Summary (< 1 page) Plan Scope (1 page) ○ Overview ○ Scope Cloud Postmigration Activities (1–2 pages) Cloud Monitoring and Management Options in AWS (1–2 pages) AWS Trusted Advisor (1–2 pages) ○ Overview ○ Feature Evaluation Summary AWS System Manager (1–2 pages) ○ Overview ○ Feature Evaluation Summary Cutover/Rollback Options (<1 page) Cloud Postmigration Recommendations (1–2 pages) Conclusion (<1 page) Check Your Evaluation Criteria 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. 9.1: Develop a plan for cloud implementation / migration. 9.5: Design a virtualized network infrastructure to meet business needs. 9.6: Design cloud storage infrastructure to meet business needs. 10.2: Create and deploy virtual machines. 10.3: Configure cloud management tools and software. 10.4: Configure cloud orchestration and automation software. 10.7: Configure a public cloud infrastructure using industry leading provider(s). 11.1: Perform system auditing. 11.5: Perform system maintenance. 11.6: Troubleshoot system problems. 11.8: Prepare contingency plans when changing cloud providers or closing down a cloud architecture. AWS amazon console https://aws.amazon.com/console/ LOGIN TO CONSOLE ID: jenny.r.goldston@gmail.com PW: tx10nesT@R* Cloud Postmigration Report Template ● ● ● ● ● ● ● ● ● Executive Summary (< 1 page) Plan Scope (1 page) ○ Overview ○ Scope Cloud Postmigration Activities (1–2 pages) Cloud Monitoring and Management Options in AWS (1–2 pages) AWS Trusted Advisor (1–2 pages) ○ Overview ○ Feature Evaluation Summary AWS System Manager (1–2 pages) ○ Overview ○ Feature Evaluation Summary Cutover/Rollback Options (<1 page) Cloud Postmigration Recommendations (1–2 pages) Conclusion (<1 page) ...
Purchase answer to see full attachment
Student has agreed that all tutoring, explanations, and answers provided by the tutor will be used to help in the learning process and in accordance with Studypool's honor code & terms of service.

Final Answer

Attached.

Running Head: CLOUD POSTMIGRATION REPORT
1

Cloud Postmigration Report
Name of Author
Institutional Affiliation
Date of Submission

CLOUD POSTMIGRATION REPORT

2

Cloud Post Migration Report
Executive Summary
The migration process takes place after careful and long planning. Preparations
have to be made to decide on the order at which organizational assets will be moved to cloud
storage. As defined, migration involves the relocation of data, applications, and any other
workloads present in an organization to the cloud. Cloud services are usually providers by large
organizations called cloud providers. One such provider is the Amazon Cloud Services popularly
referred to as the AWS. Based on the amount of data and the organization's plan, the migration
process can involve the use of multiple cloud providers. In our case, we managed to move all our
data into the AWS. The next crucial step after a successful step after the migration is the postmigration phase that has a couple of activities. This phase must take place after the migration
stage itself. There are a couple of events expected from this phase. These activities determine the
success of the step itself. Some of these activities are monitoring performance, testing,
leveraging available support, and making use of the native tools present in the cloud. We shall
thus analyze various approaches and activities associated with this phase below.
Plan Scope
Overview
A plan must be put in place to encompass the large workloads that will be moved to
AWS from BallotOnline's current servers. Before creating a migration plan, it is essential to have
a clear strategy formulated and set in place to guide the process. This, thus, makes it easier to
create a well-detailed migration plan that ensures all goes well. A policy not only outlines the
workloads to be moved but the sequence in which this must be done. This is especially important

CLOUD POSTMIGRATION REPORT

3

considering the organization still wants to maintain some of its operations while the move
happens. Therefore, the sequence is essential to ensure no data is either lost or corrupted.
Scope
The plan involves vital components of the organization's assets that need to be moved.
These fundamental elements hold within other features that make up the more significant
components. The plan thus has a list of workloads to be moved, the sequence to migrate these
workloads ranked based on importance, a timetable to guide the process, precise allocation of
roles and procedure to be performed, the performance metrics of each migration, and
communication with stakeholders. Thus, based on these elements, the workloads for our
organization are ranked based on size and complexity. This helps determine which data needs to
be moved first as well as all its dependencies. Some data loads are linked across various
applications. This makes them very complex to deal with during migration. Since we have
chosen the AWS for migration, we must then select an approach to help manage the huge
workloads present. All these are some of the considerations available in the plan. Allocation of
duties and roles to individuals and teams must also be outlined in the migration plan. The best
approach the project has is a checklist to help guide whoever is in charge of making decisions
and following through the process as tasks are crossed off the list once complete.
Cloud Postmigration Activities
As stated earlier, several activities are involved in the postmigration process.
These activities might vary from one cloud service provider to another but are all similar in some
way. Organizations should always be aware of the various events as well as challenges expected
from the postmigration phase. This helps organizations prepare adequately and in time.

CLOUD POSTMIGRATION REPORT

4

Migration is done with the hope of harnessing the various benefits associated with the move.
Cloud services have been known to save organizations a lot of money in infrastructure otherwise
deemed unnecessary. Since successful migration to the AWS cloud platform was successful, we
need to look at the various postmigration required activities. Each of these activities is meant to
ensure the proper functioning of the cloud data and application across all the layers. To further
understand the various activities involved, it is vital to first understand the cloud architecture of
our organization and its data. There are three levels in cloud architecture, i.e.;
Software a...

TutorJudithi (2665)
University of Maryland

Anonymous
Return customer, been using sp for a good two years now.

Anonymous
Thanks as always for the good work!

Anonymous
Excellent job

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4