1 Answer
- Newest
- Most votes
- Most comments
1
When defining rules for cross-account event delivery, you can only use targets that support resource access policies. Thus, you can invoke a Lambda function in a different account but not a Step Functions workflow. You would need to trigger it using another Lambda function.
With the in mind, to invoke the function you need to configure permissions so:
- The EventBridge rule on account A has an IAM execution role that allows to send events to the target on account B.
- The target resource policy on account B must explicity allow receiving events for the aforementioned execution role on account A.
You can find further details in this blog post, which covers cross-account deliver. It provides an example using Amazon SQS but it should be the same for Lambda functions.
Relevant content
- asked 24 days ago
- asked a year ago
- AWS OFFICIALUpdated a month ago
Solved:
I had problem, I followed the blog guide and yet the rule didn't triggered the Lambda, and the problem was that by mistake instead of add a Resource-based-policy to the Lambda I added a policy to the role of the Lambda.
Glad you figured it out!