What should the company do to identify the dependencies that need to be migrated in the same phase as the application?
Use AWS Migration Hub and select the servers that host the application. Visualize the network graph to find servers that interact with the application. Turn on data exploration in Amazon Athena. Query the data that is transferred between the servers to identify the servers that communicate on port 1000. Return to Migration Hub. Create a move group that is based on the findings from the Athena queries.
Use AWS Application Migration Service and select the servers that host the application. Visualize the network graph to find servers that interact with the application. Configure Application Migration Service to launch test instances for all the servers that interact with the application. Perform acceptance tests on the test instances. If no issues are identified, create a move group that is based on the tested servers.
Use AWS Migration Hub and select the servers that host the application. Turn on data exploration in Network Access Analyzer. Use the Network Access Analyzer console to select the servers that host the application. Select a Network Access Scope of port 1000 and note the matching servers. Return to Migration Hub. Create a move group that is based on the findings from Network Access Analyzer.
Use AWS Migration Hub and select the servers that host the application. Push the Amazon CloudWalch agent to the identified servers by using the AWS Application Discovery Agent. Export the CloudWatch logs that the agents collect to Amazon S3. Use Amazon Athena to query the logs to find servers that communicate on port 1000. Return to Migration Hub Create a move group that is based on the findings from the Athena queries.
Explanations:
This option effectively uses AWS Migration Hub to visualize dependencies and identify servers communicating on port 1000 through data exploration in Amazon Athena. This approach allows for an analysis of the application estate based on historical data, ensuring that all relevant dependencies are considered for migration.
While this option visualizes dependencies and tests servers, it primarily focuses on the AWS Application Migration Service for launching test instances. It does not specifically address identifying dependencies on the custom protocol over port 1000, which is crucial for understanding latency-sensitive interactions.
This option suggests using Network Access Analyzer, which is not designed for this specific scenario. Although it mentions finding servers communicating on port 1000, it does not leverage the existing application discovery data effectively and fails to integrate with AWS Migration Hub for creating a move group based on comprehensive application dependency data.
This option proposes using Amazon CloudWatch logs, which is not the most efficient method for identifying dependencies for an application migration. It involves an extra step of exporting logs and querying them, which may not directly provide insights into latency-sensitive dependencies and might complicate the identification process.
As far as I’m aware, the answer is:
Use AWS Migration Hub and select the servers that host the application. Visualize the network graph to find servers that interact with the application. Turn on data exploration in Amazon Athena. Query the data that is transferred between the servers to identify the servers that communicate on port 1000. Return to Migration Hub. Create a move group that is based on the findings from the Athena queries.