An existing RDS database must be replicated to an analytical S3 data lake.
After the initial load, INSERT, UPDATE, and DELETE changes must continue to flow.
Which configuration is most appropriate?
Use an AWS DMS task that combines full load and change data capture from RDS to S3.
Detailed explanation
Repeated full scans do not capture only changes and place unnecessary load on the source.
Repeated full scans do not capture only changes and place unnecessary load on the source.
This requires application changes and does not automatically capture transactional source changes.
This requires application changes and does not automatically capture transactional source changes.
DMS performs the initial copy and captures subsequent source changes for the target.
DMS performs the initial copy and captures subsequent source changes for the target.
A crawler discovers schema and metadata; it does not continuously replicate database changes.
A crawler discovers schema and metadata; it does not continuously replicate database changes.
Check official documentation
Compare the following points with the official documentation.
AWS DMSのfull load and CDC、RDSソース、S3ターゲットの公式説明を確認する。
What to confirm
スキーマ検出・SQL分析・イベント取り込みと、データストアのCDC複製を区別できる。
Key points
- AWS DMS
- Full load
- CDC
- RDS to S3
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Initial and ongoing phases
A replication task can seed the target and then apply changes without repeatedly scanning the full source.
Source impact
Source log retention and replication lag must be monitored so changes are not lost before capture.