Which solution meets these requirements?
Use the AWS Agentless Discovery Connector for data collection on physical servers and all VMs. Store the collected data in Amazon S3. Query the data with S3 Select. Generate reports by using Kibana hosted on Amazon EC2.
Use the AWS Application Discovery Service agent for data collection on physical servers and all VMs. Store the collected data in Amazon Elastic File System (Amazon EFS). Query the data and generate reports with Amazon Athena.
Use the AWS Application Discovery Service agent for data collection on physical servers and Hyper-V. Use the AWS Agentless Discovery Connector for data collection on VMware. Store the collected data in Amazon S3. Query the data with Amazon Athena. Generate reports by using Amazon QuickSight.
Use the AWS Systems Manager agent for data collection on physical servers. Use the AWS Agentless Discovery Connector for data collection on all VMs. Store, query, and generate reports from the collected data by using Amazon Redshift.
Explanations:
The AWS Agentless Discovery Connector does not support all types of data collection required for both physical servers and VMs, specifically Hyper-V. Additionally, while S3 Select can be used for querying data, it is not ideal for generating comprehensive reports compared to other AWS services.
The AWS Application Discovery Service agent is suitable for collecting data, but storing it in Amazon Elastic File System (Amazon EFS) is not necessary for this purpose. Amazon Athena can be used for querying, but it may not directly integrate as seamlessly with the AWS Migration Hub as other options would.
This option effectively uses the AWS Application Discovery Service agent for data collection on physical servers and Hyper-V, and the AWS Agentless Discovery Connector for VMware. Storing data in Amazon S3 allows for integration with AWS Migration Hub. Querying the data with Amazon Athena and generating reports with Amazon QuickSight are both supported and effective approaches.
While the AWS Systems Manager agent can collect data on physical servers, it is not the most suitable for virtual machines as required in the scenario. Using Amazon Redshift for reporting is excessive for the initial discovery process and may not align well with AWS Migration Hub’s capabilities for data collection and reporting.
As I recall, the answer is:
Use the AWS Application Discovery Service agent for data collection on physical servers and Hyper-V. Use the AWS Agentless Discovery Connector for data collection on VMware. Store the collected data in Amazon S3. Query the data with Amazon Athena. Generate reports by using Amazon QuickSight.