Question

A logistics company is migrating a 90 TB on-premises PostgreSQL database to Amazon RDS for PostgreSQL. The company's WAN link to AWS is a 500 Mbps connection that is also used for production traffic during business hours, leaving only about 200 Mbps of usable bandwidth for migration. Business rules require the application to remain read-write until a hard 6-hour cutover window on a weekend, during which only minimal downtime is acceptable. The solutions architect must move the bulk data and then apply ongoing changes so the cutover fits within the window. Which approach best meets these requirements?

Accepted Answer

Export the full database to an AWS Snowball Edge device, ship it to AWS to load the bulk data into RDS, and configure an AWS DMS change data capture (CDC) task from the source to keep the target synchronized until the cutover window.

Answer

Run a single AWS DMS full-load task over the existing WAN link, scheduling it to complete before the weekend cutover window and cutting over once the full load finishes.

Answer

Use AWS DataSync to copy the PostgreSQL data files to Amazon S3 over the WAN link, then restore the files directly into the RDS instance during the cutover window.

Answer

Take a native pg_dump during the 6-hour cutover window, transfer the dump file over the WAN link, and restore it into RDS before reopening the application for writes.