Replies: 1 comment
|
Thanks @ghost-oss, the repro is exactly right: Floci stores a Kinesis stream target but has no delivery path for it, so the event is dropped with that warning. This is a real AWS target type, so it belongs in Floci. I opened #8553 to track it, and a PR that closes it is welcome. Two details from the model worth getting right: There was an earlier attempt in #6866 that went stale, so its review is a useful checklist. Please sign the commits and fill in the PR template. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What we'd like
We'd like EventBridge rules in Floci to deliver matching events to a Kinesis Data Stream, the same way they already deliver to SQS, SNS, Lambda and Firehose. Real AWS supports this (the Arn of a target can be a Kinesis stream ARN, with optional KinesisParameters.PartitionKeyPath).
Current behaviour
PutTargets accepts a Kinesis stream ARN, and ListTargetsByRule returns it.
When an event matches, nothing is written to the stream. The log shows EventBridge: unsupported target ARN type: arn:aws:kinesis:....
Repro
aws kinesis create-stream --stream-name orders-stream --shard-count 1
aws events put-rule --name orders-to-kinesis --event-pattern '{"source":["app.orders"]}'
aws events put-targets --rule orders-to-kinesis --targets '[{
"Id":"kinesis",
"Arn":"arn:aws:kinesis:us-east-1:000000000000:stream/orders-stream",
"RoleArn":"arn:aws:iam::000000000000:role/events-kinesis",
"KinesisParameters":{"PartitionKeyPath":"$.detail.orderId"}
}]'
aws events put-events --entries '[{"Source":"app.orders","DetailType":"OrderCreated","Detail":"{"orderId":"123"}"}]'
Expected: a record with partition key "123" on orders-stream. Actual: no record.
All reactions