1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
We might need more data regarding the behavior to correctly gauge what is wrong.
But it might be that API Gateway does not have the appropriate permissions set in its execution role. You might need to provide SQS SendMessage permissions to the role that the API in API Gateway uses.
You might find this third party article useful:
https://dzone.com/articles/creating-aws-service-proxy-for-amazon-sqs
Let us know if this helps!
answered 6 years ago
Relevant content
- Accepted Answerasked 9 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a month ago