An on-premises database must be migrated to AWS while the business continues operating.
The team wants to minimize downtime during the final cutover.
Which migration approach fits the requirement?
AWS Database Migration Service (AWS DMS) can use ongoing replication to keep the target synchronized with source changes and reduce cutover downtime.
Detailed explanation
Organizations manages accounts and consolidated billing; it does not migrate or transform database data.
Organizations manages accounts and consolidated billing; it does not migrate or transform database data.
CloudFront is a content delivery service, not a database migration or replication service.
CloudFront is a content delivery service, not a database migration or replication service.
Manual entry is not a practical or reliable approach for a large database migration and creates integrity and schedule risks.
Manual entry is not a practical or reliable approach for a large database migration and creates integrity and schedule risks.
AWS DMS supports database migration and can continuously replicate changes so the final cutover can be shorter.
AWS DMS supports database migration and can continuously replicate changes so the final cutover can be shorter.
Check official documentation
Compare the following points with the official documentation.
AWS Database Migration Serviceの移行方式と継続的レプリケーションを確認する。
What to confirm
稼働中データベースの停止時間を抑える移行方式としてAWS DMSを説明できる。
Key points
- AWS DMS
- Ongoing replication
- Cutover downtime
Notes
- Environment: AWS公式Database Migration Serviceドキュメントの確認
- Confirm current AWS migration guidance and service conditions in the official documentation.
Foundation review
Synchronization before cutover
Keeping the target current allows the final switch to be short and controlled.
Migration role
A content-delivery or account-management service does not provide database replication.