Several JSON objects are concatenated into one record sent to Firehose.
Split the objects into individual records before S3 delivery, transformation, and partitioning.
Which feature is most appropriate?
Use Firehose multi-record deaggregation to split aggregated JSON or delimited data into individual user records.
Detailed explanation
The feature splits concatenated JSON or delimited data into individual records for downstream processing.
The feature splits concatenated JSON or delimited data into individual records for downstream processing.
Athena queries stored data and is not a Firehose pre-delivery deaggregation step.
Athena queries stored data and is not a Firehose pre-delivery deaggregation step.
LOB modes control large-column transfer and do not split multiple JSON objects in a Firehose record.
LOB modes control large-column transfer and do not split multiple JSON objects in a Firehose record.
Object Lock controls retention and deletion protection, not record parsing.
Object Lock controls retention and deletion protection, not record parsing.
Check official documentation
Compare the following points with the official documentation.
Amazon Data Firehoseの複数レコードデータデアグリゲーションとJSON形式の公式説明を確認する。
What to confirm
送信側の集約と配信側のデアグリゲーションの役割を説明できる。
Key points
- Deaggregation
- JSON
- Firehose
- Individual record
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Aggregate and split
Transport aggregation reduces overhead, while deaggregation restores units needed for transformation and partitioning.
Format contract
The aggregation format and delimiters must match the Firehose deaggregation configuration.