Which solution will provide the required TCO information?
Request access to Migration Evaluator. Run the Migration Evaluator Collector and import the data. Configure a scenario. Export a Quick Insights report from Migration Evaluator.
Launch AWS Database Migration Service (AWS DMS) for the on-premises database. Generate an assessment report. Create an estimate in AWS Pricing Calculator for the costs of the EKS migration.
Initialize AWS Application Migration Service. Add the on-premises servers as source servers. Launch a test instance. Output a TCO report from Application Migration Service.
Access the AWS Cloud Economics Center webpage to assess the AWS Cloud Value Framework. Create an AWS Cost and Usage report from the Cloud Value Framework.
Explanations:
Migration Evaluator is specifically designed to help estimate TCO for migrating workloads to AWS. It allows users to collect data, configure migration scenarios, and generate detailed reports on costs. This option directly addresses the need for TCO information for the migration to EKS and RDS.
AWS Database Migration Service (DMS) is used primarily for migrating databases rather than estimating TCO. While it can generate reports related to database migration, it does not provide a comprehensive TCO estimation for the entire workload including EKS.
AWS Application Migration Service is focused on migrating servers and generating reports related to that process. It does not specifically provide TCO information for workloads, especially not for containerized applications and databases.
The AWS Cloud Economics Center and the AWS Cloud Value Framework provide insights on cost management and cloud value but do not directly calculate TCO for specific workloads or migrations. A Cost and Usage report alone is insufficient for estimating TCO in this context.
Based on what I know, the answer is:
Request access to Migration Evaluator. Run the Migration Evaluator Collector and import the data. Configure a scenario. Export a Quick Insights report from Migration Evaluator.