An enterprise is planning to migrate a critical media management platform to AWS within a tight 3-month timeline. The platform consists of the following components:
1. DRM Licensing Engine: Runs on Windows Server 2012 R2. It uses a proprietary hardware-bound licensing mechanism requiring specific kernel-level driver access and physical motherboard signatures that cannot be virtualized or emulated on cloud hypervisors.
2. Video Encoding System: A resource-intensive custom C++ application that processes raw video streams using GPU acceleration. The enterprise plans to modernize this to a serverless architecture using AWS Elemental MediaConvert and AWS Lambda in the future, but current resource constraints prevent any code changes or refactoring during the 3-month migration phase.
3. Metadata Catalog: Runs on a highly customized on-premises Microsoft SQL Server database. It utilizes proprietary SQL Server Common Language Runtime (CLR) integration and extensive SQL Server Integration Services (SSIS) packages for data processing. The business wants to migrate this catalog to Amazon Aurora PostgreSQL to eliminate commercial licensing costs and reduce administrative overhead, which requires complete schema conversion and rewriting of the CLR/SSIS logic.
4. Web Frontend: A stateless Node.js application running on Ubuntu VMs. The enterprise wants to migrate this component to AWS to minimize operating system management overhead, but they must keep the application code unchanged.
Which combination of migration strategies represents the most appropriate path for each component to meet the enterprise's requirements and timeline?
- ARehost the DRM Licensing Engine to Amazon EC2 bare-metal instances; Rehost the Video Encoding System to GPU-enabled Amazon EC2 instances; Replatform the Metadata Catalog by migrating it to Amazon Aurora PostgreSQL; Refactor the Web Frontend by rewriting the Node.js application to run on AWS Lambda.
- Retain the DRM Licensing Engine on-premises; Rehost the Video Encoding System to GPU-enabled Amazon EC2 instances; Refactor the Metadata Catalog by converting the database engine to Amazon Aurora PostgreSQL, converting the schema, and rewriting CLR and SSIS logic; Replatform the Web Frontend by containerizing it to run on Amazon ECS with AWS Fargate.Answer
- CRetain the DRM Licensing Engine on-premises; Replatform the Video Encoding System by migrating it to AWS Elemental MediaConvert and AWS Lambda; Replatform the Metadata Catalog by migrating it to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT); Rehost the Web Frontend to Amazon EC2 instances running Ubuntu.
- DRetain the DRM Licensing Engine on-premises; Refactor the Video Encoding System by containerizing it to run on AWS Fargate; Rehost the Metadata Catalog by migrating it to Amazon EC2 instances running SQL Server; Replatform the Web Frontend by containerizing it to run on Amazon ECS with AWS Fargate.