An enterprise is planning to migrate its core financial auditing platform to AWS within a strict six-month timeline. The workload consists of three primary components:
1. A web frontend running Apache Tomcat on Windows Server 2012 R2. The operating system has reached End-of-Support (EOS). To comply with corporate security standards, the OS must be upgraded to Windows Server 2022 during the migration, but the application code itself will not be modified.
2. A transactional database running on Microsoft SQL Server 2016. To eliminate commercial licensing costs, the enterprise wants to migrate this database to Amazon Aurora PostgreSQL, which will require converting the database schema and rewriting legacy stored procedures.
3. A legacy reporting system that requires a physical hardware security module (HSM) with proprietary on-premises API integrations that cannot be virtualized or replicated in the cloud, but must remain operational for auditing purposes.
Which combination of migration strategies represents the most appropriate alignment with the AWS 7 Rs framework for these components?
- Replatform the web frontend to upgrade the operating system; Refactor the transactional database to Aurora PostgreSQL; Retain the legacy reporting system on-premises.Answer
- BRehost the web frontend by migrating the virtual machine as-is; Replatform the transactional database by deploying SQL Server on Amazon RDS; Retire the legacy reporting system.
- CReplatform the web frontend to upgrade the operating system; Replatform the transactional database to Aurora PostgreSQL; Retain the legacy reporting system on-premises.
- DRehost the web frontend to Windows Server 2022; Refactor the transactional database to Aurora PostgreSQL; Replatform the legacy reporting system using AWS hardware emulation.