JSON logs received by Firehose contain fields that should be removed before delivery to S3.
Keep transformation scaling and retries in the Firehose flow.
Which configuration is most appropriate?
Configure a Lambda function as the Firehose data transformation processor.
Detailed explanation
Firehose invokes Lambda to transform records and then delivers successful results to S3.
Firehose invokes Lambda to transform records and then delivers successful results to S3.
CloudTrail audits AWS API activity and does not transform arbitrary S3 objects.
CloudTrail audits AWS API activity and does not transform arbitrary S3 objects.
ViewType controls DynamoDB change images and does not transform Firehose records.
ViewType controls DynamoDB change images and does not transform Firehose records.
Athena queries stored data and is not a pre-delivery Firehose processor.
Athena queries stored data and is not a pre-delivery Firehose processor.
Check official documentation
Compare the following points with the official documentation.
Amazon Data FirehoseのLambdaデータ変換、成功・失敗レコード処理の公式説明を確認する。
What to confirm
配信前変換と、保存後のクエリ・監査ログの役割を区別できる。
Key points
- Firehose data transformation
- Lambda
- Pre-delivery processing
- Failed records
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Transformation position
Transforming before delivery changes the landing data; post-landing ETL has different latency and replay characteristics.
Failure handling
Backups, retries, and error output protect records that a transformation cannot process.