- Newest
- Most votes
- Most comments
Certainly the permission looks correct; and as you say you can substitute POST
with *
and it should still work. Going into API Gateway and re-selecting the Lambda function as a target will replace the permissions so that's worth a try.
is it possible there are some guardrails in your account that are "remediating" your configuration? Yes. But from this distance it's not possible to tell for sure. CloudTrail will show changes in the account so it might be worth looking there to see if any changes are showing up.
Other than that: Create a support ticket. The support team has the ability to see what is running in the account and what is happening.
Yes the source ARN looks correct.
Just to be sure, you are running out of us-east-1 right? As that is in your ARN. Also the action is set to lambda:InvokeFuction?
Relevant content
- asked 4 years ago
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago