Copy DynamoDB history to S3 for Athena analysis.
Avoid consuming table read capacity and export from a point-in-time backup.
Which feature is most appropriate?
Use DynamoDB Export to S3 from a point-in-time backup for an analytical copy.
Detailed explanation
The export reads a backup and avoids the same online Scan load on the source table.
The export reads a backup and avoids the same online Scan load on the source table.
Audit events do not contain the complete table data.
Audit events do not contain the complete table data.
A full Scan consumes capacity, takes time, and adds throttling risk.
A full Scan consumes capacity, takes time, and adds throttling risk.
S3 Lifecycle manages objects and does not export DynamoDB items.
S3 Lifecycle manages objects and does not export DynamoDB items.
Check official documentation
Compare the following points with the official documentation.
DynamoDB Export to S3、PITR、S3形式・暗号化の公式説明を確認する。
What to confirm
オンラインScanとバックアップベースのエクスポート、S3管理機能を区別できる。
Key points
- DynamoDB Export to S3
- PITR
- Analytical copy
- Read capacity
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Online versus backup export
Backup-based export limits application read impact compared with an application Scan.
Downstream format
Choose an output format, encryption, and partitioning suitable for the analytical consumer.