1 個回答
- 最新
- 最多得票
- 最多評論
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!
已回答 6 年前
相關內容
- 已提問 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前