Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Dynamic Path Integration for API Gateway and SQS
I'm seeking help with dynamically overriding the path on API Gateway to connect to different SQS queues on demand.
If I use the URL of an existing SQS Queue, everything works fine (roles and permissions are in place), and I'm logging API Gateway activity to Cloudwatch. Here's what I've done so far:
-
Using VTL: I assigned a dynamic value to QueueUrl. Cloudwatch logs show the correct dynamic value (constructed from query strings), but the request is sent to the "path override" parameter configured on API Gateway.
-
Using VTL: I tried to override the path using $context.requestoverride object but encountered an error, unable to modify the request.
Is there a way to make this parameter dynamic? Creating an endpoint for each SQS queue (potentially thousands) isn't practical, and I want to avoid using a single SQS queue with client-side filtering.
Any suggestions?
- Newest
- Most votes
- Most comments
Yes you can do it in this way.
- Configure the Path Override parameter: While configuring the integration on Path Override, you need to define it like 12345678/{queueId} where 12345678 is your account id.
- Define URL PATH Parameters: You need to define URL PATH Parameters. Name queueId, Mapped from method.request.path.queueId1.
- Add HTTP headers: Expand HTTP headers and add a new Header with Name Content-Type, Mapped from 'application/x-www-form-urlencoded'.
- Add a Mapping Template: Add a Mapping Template as Content-Type application/json and template body as Action=SendMessage&MessageBody=$input.body.
Here you can find an old post about it: https://stackoverflow.com/questions/75197213/routing-message-from-aws-api-gateway-to-sqs-regarding-url-path
Hi,
A solution is also to use EventBridge to dynamically route to different queues as a second stage.
Best,
Didier
I was able to solve it directly through API Gateway, but I appreciate learning about your approach. I'll definitely keep it in mind for future endeavors. Thank you!
Relevant content
- asked 2 years ago
Oh, it’s working now! I was starting to think it wasn’t possible. It seems the issue was using a query string instead of a path parameter.
Thank you very much for your help!