1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
You should follow this service-neutral guidance and full example to achieve cross-account calls with Lambdas: https://gist.github.com/helephant/57d10c022f22e8209118b459a5afb60d
Best,
Didier
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
Thank you Didier.
This solution involves invoking 2 lambdas, one acting like a proxy to bridge the permission issue.
Is there no way to use just 1 lambda in account A that can be called from a service like Pinpoint in account B? Pinpoint internally calls a lambda during a campaign / journey. This is specified through the Pinpoint API as an ARN string. I have tried giving the ARN of the lambda in account A, along with relaxing the permissions for this lambda to allow incoming requests from Pinpoint in account B, but this does not seem to work.
Can you positively confirm that Pinpoint campaign / journey lambda invocations cannot be done cross-account through a single lambda invocation?