2 Answers
- Newest
- Most votes
- Most comments
0
I assume you have your Connection authorized, if not, then you should fix the token acquisition first
If you have WAF Rule configured, this gets your requests blocked. If so you would need to adjust them to allow the access.
answered 2 years ago
0
Hey sorry if you've looked elsewhere. But I believe the answer is that you need a policy attached to your Rule that allows it to invoke your Destination.
Your role should have a policy that has a stanza like this:
{
"Effect": "Allow",
"Action": [
"events:InvokeApiDestination"
],
"Resource": [
"arn:of:your:destination"
]
}
I got the answer from this cloudformation/serverless example.
Hope it helps.
answered 2 years ago
Relevant content
- Accepted Answerasked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
By "Connection Authorized", do you mean the endpoint requires authentication? If so, then yes, my live endpoint requires authentication and I have the right token set up in the Connection. I also don't have any WAF rules defined.
For testing, I have set up an ngrok instance that proxies requests to a local server on my machine. It does not require any authorization, and I am able to hit it from curl and from the browser. EventBridge fails to invoke it with the same NO_PERMISSIONS error.