Which solution will meet these requirements?
Use AWS Server Migration Service (AWS SMS) and AWS Database Migration Service (AWS DMS) to evaluate migration. Use AWS Service Catalog to understand application and database dependencies.
Use AWS Application Migration Service. Run agents on the on-premises infrastructure. Manage the agents by using AWS Migration Hub. Use AWS Storage Gateway to assess local storage needs and database dependencies.
Use Migration Evaluator to generate a list of servers. Build a report for a business case. Use AWS Migration Hub to view the portfolio. Use AWS Application Discovery Service to gain an understanding of application dependencies.
Use AWS Control Tower in the destination account to generate an application portfolio. Use AWS Server Migration Service (AWS SMS) to generate deeper reports and a business case. Use a landing zone for core accounts and resources.
Explanations:
AWS Server Migration Service (AWS SMS) and AWS Database Migration Service (AWS DMS) are primarily focused on the actual migration of applications and databases rather than assessing and understanding the existing portfolio. AWS Service Catalog is not specifically designed to analyze application and database dependencies, making this option inadequate for the initial assessment needed before migration.
AWS Application Migration Service is used for migrating applications, but it requires prior knowledge of the applications to set up agents. AWS Migration Hub helps track migrations but doesn’t provide deep insights into the current portfolio. AWS Storage Gateway is not relevant for assessing database dependencies, making this option less suitable for gaining a comprehensive understanding of the existing application and database landscape.
Migration Evaluator provides insights into the current environment by generating a list of servers and associated costs, which is useful for building a business case. AWS Migration Hub offers a centralized view of migration progress, and AWS Application Discovery Service helps identify application dependencies, making this option the most effective for understanding the portfolio prior to migration.
AWS Control Tower is designed for setting up and governance of AWS accounts but does not generate an application portfolio. While AWS SMS can help with migration, it does not provide the initial assessment of application dependencies. This option does not adequately address the requirement to assess the existing portfolio before migration.
My best guess is:
Use Migration Evaluator to generate a list of servers. Build a report for a business case. Use AWS Migration Hub to view the portfolio. Use AWS Application Discovery Service to gain an understanding of application dependencies.
I weigh that the answer is:
Use Migration Evaluator to generate a list of servers. Build a report for a business case. Use AWS Migration Hub to view the portfolio. Use AWS Application Discovery Service to gain an understanding of application dependencies.