Which strategy should the solutions architect choose to perform this migration?
Create a fleet of EC2 instances. Install MongoDB Community Edition on the EC2 instances, and create a database. Configure continuous synchronous replication with the database that is running in the on-premises data center.
Create an AWS Database Migration Service (AWS DMS) replication instance. Create a source endpoint for the on-premises MongoDB database by using change data capture (CDC). Create a target endpoint for the Amazon DocumentDB database. Create and run a DMS migration task.
Create a data migration pipeline by using AWS Data Pipeline. Define data nodes for the on-premises MongoDB database and the Amazon DocumentDB database. Create a scheduled task to run the data pipeline.
Create a source endpoint for the on-premises MongoDB database by using AWS Glue crawlers. Configure continuous asynchronous replication between the MongoDB database and the Amazon DocumentDB database.
Explanations:
While creating EC2 instances and installing MongoDB Community Edition could theoretically allow for replication, this method introduces unnecessary complexity and management overhead. It also does not utilize AWS-native services for migration, which would be more efficient and reliable.
AWS Database Migration Service (AWS DMS) is designed for migrating databases to AWS, including change data capture (CDC) capabilities that enable real-time data replication. This option directly supports the migration from the on-premises MongoDB database to Amazon DocumentDB, making it the most suitable and efficient choice.
AWS Data Pipeline is not specifically designed for real-time database migration and does not inherently support change data capture for ongoing replication. It is better suited for batch processing rather than continuous replication of live databases.
AWS Glue is primarily used for data integration and transformation rather than direct database migration. It does not support continuous replication like AWS DMS does, making it an inappropriate choice for migrating an operational MongoDB database to Amazon DocumentDB.
I scheme that the answer is:
Create an AWS Database Migration Service (AWS DMS) replication instance. Create a source endpoint for the on-premises MongoDB database by using change data capture (CDC). Create a target endpoint for the Amazon DocumentDB database. Create and run a DMS migration task.