- Newest
- Most votes
- Most comments
Hi,
As you have observed, it's not possible to set a Kinesis Delivery Stream to consume from a Kinesis Data Stream in a different account. I believe a similar constraint would prevent the Event Bridge Pipes method.
To keep the serverless approach, you can use AWS Lambda to consume and process from the data stream, as native integration is provided that handles polling, checkpointing etc. You may find this blog useful - https://aws.amazon.com/blogs/big-data/best-practices-for-consuming-amazon-kinesis-data-streams-using-aws-lambda/
There is also the option to deploy the Kinesis Data Firehose in Account A and deliver to a target in Account B, for an example walkthrough of this, see https://repost.aws/knowledge-center/kinesis-firehose-cross-account-streaming
Hope that helps!
Hello,
Yes, there is no direct integration, but, couple of things can be done - write a lambda function in Account A listening for updates on the Stream and then write to Firehose in Account B (via cross account assume role). OR If Account A can directly write to Account B S3 bucket (if that is the end goal) then that is also simpler.
You may also want to check this link for more insights - https://docs.aws.amazon.com/managed-flink/latest/java/examples-cross.html
Relevant content
- asked 7 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago