Aws help
Your 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 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.
Your supervisor, Sophia, has recommended that you use your Cloud Adoption Policy Addendum from CCA 630: Cloud Infrastructure Planning, Design, and Configurations, as you are looking at migration considerations.
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.
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
· After reviewing and creating the feature comparison table for the above-listed tools, submit your comparison via the dropbox below using the Premigration Assessment Tool Comparison Template .
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.
After reviewing the AWS Application Discovery Services website, engage in an online conversation with your colleagues at BallotOnline in the Discussion: Evaluation of AWS Application Discovery Service and then continue to the next step to install a discovery agent.
Step 4: Install AWS Application Discovery Agent
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.
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 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.
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. 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. 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.
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.
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 and submit it via the dropbox below.