- Le plus récent
- Le plus de votes
- La plupart des commentaires
To set the integration request parameters dynamically based on event data in an Amazon API Gateway WebSocket API, you can use the Velocity Template Language (VTL) in the integration request mapping template.
Here is an example integration request mapping template that sets the body, query, headers, and path parameters of the integration request based on the event data:
#set($inputRoot = $input.path('$')) { "body" : "$inputRoot.body", "query" : { #foreach($param in $inputRoot.query.keySet()) "$param" : "$inputRoot.query.get($param)" #if( $foreach.hasNext ),#end #end }, "headers" : { #foreach($param in $inputRoot.headers.keySet()) "$param" : "$inputRoot.headers.get($param)" #if( $foreach.hasNext ),#end #end }, "path" : { #foreach($param in $inputRoot.path.keySet()) "$param" : "$inputRoot.path.get($param)" #if( $foreach.hasNext ),#end #end } }
This template first sets the $inputRoot variable to the root of the input event data. It then sets the body, query, headers, and path parameters of the integration request to the corresponding values in the event data.
You can then use this integration request mapping template in the integration request of your WebSocket API to dynamically set the integration request parameters based on the event data.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
That didn't work for me and it seems maybe that only the REST or HTTP version of Gateway supports this. I can't quite understand why this wouldn't be supported in the websocket API, but the documentation clearly leaves it out so I wasn't surprised when it didn't work.