Question

A retail company runs a self-managed MySQL 8.0 database on-premises that powers an order-processing application. The analytics team needs a copy of the order tables in Amazon S3, stored in Apache Parquet format, so they can run Amazon Athena queries. The requirement is that S3 must reflect both the existing historical data and any changes made in MySQL going forward, with a delay of no more than a few minutes. The source database must remain online for production use throughout, and the solution should minimize custom code and ongoing operational effort. Which approach best meets these requirements?

Accepted Answer

Use AWS DMS with a full load plus ongoing replication (CDC) task, an S3 target endpoint configured to output Parquet, and enable MySQL binary logging on the source.

Answer

Use AWS DataSync to copy the MySQL data directory to S3 on a scheduled task, then convert the files to Parquet with an AWS Glue job.

Answer

Use AWS DMS with a full-load-only task to S3 in Parquet format, and re-run the task nightly to capture new changes.

Answer

Export mysqldump files to an S3 bucket via a cron job, then trigger an AWS Lambda function to convert each dump to Parquet.