- Le plus récent
- Le plus de votes
- La plupart des commentaires
There are some good tutorials that can help you understand how to configure API Gateway - https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-rest-tutorials.html
Kinesis DF expects a specific response format - see https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html for details. The same responseId from the request sent to a HTTP destination must exist as well in the response. If you can not influence HTTP destination so it replies with the expected format you can use API Gateway Rest API with the integration type of HTTP. There you can define VTL templates to map responses from the target. The only way I know to remember requestId between the request and the response is to add an integration request template
#set($context.requestOverride.header.request-id = $util.parseJson($input.body).requestId)
$input.json('$')
and then in the integration response template:
#set($requestId = $context.requestOverride.header.request-id)
{
"requestId": "$requestId",
"timestamp": $context.requestTimeEpoch
}
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a 13 jours
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 6 mois
@UdAWS - If my answer has helped you understand API Gateway better, can I request you to please accept my answer. Thanks