Hi Solace community,
We’re working on a PoC integration between Solace PubSub+ Cloud (trial tier) and Amazon Kinesis Data Streams and have a few questions about what’s possible with RDPs.
Our goal:
Connect a Solace RDP directly to the Kinesis Data Streams REST API (https://kinesis.us-east-1.amazonaws.com) to put messages onto a stream without a Lambda shim in between.
What we know RDP supports:
-
AWS SigV4 authentication (confirmed in docs)
-
Custom request headers (e.g.
X-Amz-Target: Kinesis_20130901.PutRecord,Content-Type: application/x-amz-json-1.1) -
Substitution expressions in headers and POST request targets
The blocker:
The Kinesis PutRecord API requires this specific request body format:
{
"StreamName": "my-stream",
"PartitionKey": "some-key",
"Data": "<base64-encoded-payload>"
}
Our Solace message payload is raw JSON. For the RDP to call Kinesis directly, it would need to wrap the payload in this envelope and base64-encode the Data field.
Our questions:
-
Is there any way to configure an RDP to transform or wrap the outgoing message body before sending — for example using substitution expressions or any other mechanism?
-
If not, is this something supported on higher tiers or via any Solace connector?
-
We noticed the
base64()function exists in substitution expressions — is this usable in any way that could help here?
We’re aware of the Solace Kinesis connector (micro-integration runtime) as an alternative, but are trying to understand if a pure RDP-based approach is feasible first.
Thanks in advance!