A company is planning to migrate a legacy document processing application to AWS within a strict 6-month timeline. The application consists of three tiers:
1. A web tier running Apache HTTP Server on Red Hat Enterprise Linux 7 virtual machines.
2. A processing tier running a Java-based document parsing engine on IBM AIX servers. The engine utilizes a proprietary native C-shared library for file parsing and requires POSIX-compliant local filesystem access. The company cannot rewrite the core logic due to budget and time constraints.
3. A database tier running Oracle Database 19c on-premises, using proprietary Oracle Spatial features for document metadata geotagging. The company wants to eliminate commercial database licensing costs and is willing to convert the database schema and modify application SQL queries.
Which combination of migration strategies (7 Rs) represents the most appropriate and feasible migration path for this application?
- Rehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the processing tier by recompiling the C-shared library and running the Java application on x86_64 Amazon Linux 2 EC2 instances; Refactor the database tier by converting the Oracle schema and migrating to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS).Cevap
- BRehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Rehost the processing tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the database tier to Amazon Aurora PostgreSQL using AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS).
- CRehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the processing tier by running the Java application on x86_64 Amazon Linux 2 EC2 instances; Replatform the database tier to Amazon Aurora PostgreSQL using AWS Database Migration Service (DMS) to minimize code changes.
- DReplatform the web tier by containerizing the Apache server on Amazon ECS; Refactor the processing tier by rewriting the core Java logic and POSIX file operations to use AWS Lambda and Amazon S3; Rehost the database tier to Amazon RDS for Oracle.