- 最新
- 投票最多
- 评论最多
DynamoDB Streams and AWS Lambda triggers states the following:
You cannot use the same Lambda trigger across different AWS accounts. Both the DynamoDB table and the Lambda functions must belong to the same AWS account.
While this is true, there is a simple work-around which requires 1 extra Lambda. In Account A where the table is placed, have a Lambda consume from the stream, this Lambda will simply invoke a Lambda in Account B. There is a slight bit of latency included, however, you can achieve the same semantics as DynamoDB Stream directly invoking a Lambda in Account B.
DynamoDB CRUD
-> Stream
-> Lambda Acc A
-> Lambda Acc B
Answering my own question here. The Lambda and DynamoDB table must be on the same account and cross-account triggers on DynamoDB streams is not yet supported.
While not ideal, we have decided to place the Lambda in the same account as the DynamoDB.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 10 个月前
Hi, yes, doc that you point to is clear about it.