fix: Lambda function invoke for async #140
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The async policy is missing the action to asynchronously call other lambda functions.
Description
Added lambda:InvokeFunction into the policy document for async integrations
Motivation and Context
When I deployed a lambda of which the
destination_on_success
is another lambda arn, my caller lambda failed to call my callee lambda due to a permission error.Breaking Changes
Does not break changes
How Has This Been Tested?
After adding the above changes on my local terraform module, the lambda integration works as expected.