1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Could you check that you have configure the request mapping template as follows? I also recommend that you take a look at the following Knowledge Center article, or the following blog, which describe how to carry out the integration between a REST API Gateway and Amazon SQS.
Action=SendMessage&MessageBody=$input.body
Updated: According to the following Knowledge Center article, if the AWS service API expects a resource path in the request, you should use the path override options, and the SendMessage operation requieres it. In contrast, Kinesis PutRecord or SNS Publish operations could use the action name, since they don't expect a resource path.
Relevant content
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 years ago
Yes, I did the same..
Can you give more information to help you find the solution?
Just compare integrating apigateway-sqs with integrating apigateway-firehose
Hi,
According to the following Knowledge Center article, if the AWS service API expects a resource path in the request, you should use the path override options, and the SendMessage operation requieres it. In contrast, Kinesis PutRecord or SNS Publish operations could use the action name, since they don't expect a resource path. I hope this helps you.