- Newest
- Most votes
- Most comments
The HTTP API only supports sending data to Kinesis via the PutRecord API, while the REST API supports both PutRecord and PutRecords. If you need to use the putRecords
endpoint to batch multiple records in a single API call, you would need to use the REST API Gateway or implement custom backend logic to handle batching.
If you're looking for lower latency and higher throughput, why not call the Kinesis Data Stream service directly? This might mean that you need to use some temporary (and appropriately scoped to a essential permissions only) credentials to the client but that should not be terribly difficult as I'm assuming that the existing/planned API is not going to be used anonymously. So you'll need to vend the credentials but then the client can use the service without having to go through a separate API service.
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 6 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
Thank you @brettski-AWS ! My calling system is a legacy ERP system ! I guess I will have to research what capabilities they might have to make this call directly to KDS since any kind of SDK integration will be out of the question here for them.