- 新しい順
- 投票が多い順
- コメントが多い順
Thank you for reaching out to us. Firehose does have some latency due to buffering hints[1] in the service. Having Kinesis stream connector to kinesis analytics takes care of checkpoints/batching and this can be read by lambda and written to SNS. The architecture is as below:
Kinesis analytics --> Kinesis stream --> lambda --> SNS
Please refer to the below blog for example architecture : -- https://aws.amazon.com/blogs/big-data/building-a-real-time-notification-system-with-amazon-kinesis-data-streams-for-amazon-dynamodb-and-amazon-kinesis-data-analytics-for-apache-flink/
Please note that de-duplication should be done on consumer end. This can be done in lambda function in the above case. Let us know if you may have any other queries.
References
[1] https://docs.aws.amazon.com/firehose/latest/APIReference/API_BufferingHints.html
関連するコンテンツ
- AWS公式更新しました 2年前
- AWS公式更新しました 4年前