A financial services enterprise is planning to migrate its core application portfolio to AWS. The portfolio consists of three key components:
1. A monolithic Java application running on Apache Tomcat. The application code cannot be modified due to a strict 3-month migration window and a lack of Java development resources. However, the company wants to minimize server administration overhead on AWS.
2. A backend transactional database running on Oracle Database EE. To reduce ongoing operational expenditures, the executive leadership has mandated the complete elimination of proprietary database licensing costs. The migration team has been allocated a separate 9-month timeframe to perform comprehensive schema conversions and rewrite database-interacting application queries.
3. A legacy COBOL reporting system running on an aging mainframe. Due to compliance requirements, the historical ledger data must remain accessible once a year. The source code is lost, and the system cannot be simulated or migrated to the cloud.
Which combination of migration strategies under the 7 Rs framework should the solutions architect recommend to meet all requirements?
- ARehost the Java application on Amazon EC2; Rehost the Oracle database to Amazon RDS for Oracle; Retire the legacy COBOL reporting system.
- BReplatform the Java application to Amazon ECS on AWS Fargate; Replatform the Oracle database by migrating it to Amazon Aurora PostgreSQL; Retain the legacy COBOL reporting system on-premises.
- Replatform the Java application to Amazon ECS on AWS Fargate; Refactor the Oracle database by converting the schema and migrating to Amazon Aurora PostgreSQL; Retain the legacy COBOL reporting system on-premises.Answer
- DRefactor the Java application by rewriting it into AWS Lambda functions; Refactor the Oracle database by migrating to Amazon Aurora PostgreSQL; Rehost the legacy COBOL reporting system using AWS Mainframe Modernization.