A thought based on the question: Kinesis and SQS operate differently. So when you say "the shard will be blocked" - individual consumers on the shard might choose not to consume the next message in the stream but there's no concept of "blocking". Unlike SQS, messages in the stream are visible to all of the consumers so they can choose what they're going to do with each message - which is great if you have several different processes that need to happen on a single message - you can use different consumers and they don't get in each other's way.
So in the Kinesis world, if you want to maintain ordering you can only have a single consumer on the stream (shard, really). If there is a fault the blocking happens in the consumer, not in Kinesis.
Probably not helpful - but I'd question why Kinesis is better than SQS FIFO in this case.
Finally: I'm a little concerned about the comment "SQS FIFO is too slow" - have you tested Kinesis to ensure that it meets your performance requirements?
Given the complexity of the question and the challenges you appear to be facing I'd contact your local AWS Solutions Architect to discuss further...
Relevant questions
Why does the Kinesis Firehose output "Throttling error encountered when calling Kinesis".
asked 3 months agoHow do we turn off SMPP delivery message when using Pinpoint and SNS for 2 way SMS?
asked 5 months agoHow is SNS guaranteed to receive messages from event sources?
Accepted Answerasked 2 months agoguaranteed delivery of events with intermittently offline Device
Accepted Answerasked 5 months agoKinesis fan-out
Accepted AnswerHow to set the starting position for a Kinesis Delivery Stream
asked 18 days agoPicking the correct Opensearch index date from the Kinesis Delivery Stream
asked 18 days agoOrdered message delivery to downstream consumers when transient faults occur
asked 5 months agoDynamo DB Kinesis Steams Best Practice
Accepted Answerasked a year agoMultiple Kinesis Data Analytics apps to use the same Kinesis firehose delivery stream as source
Accepted Answerasked 2 years ago
Hi there, thanks for replying.
Regsarding SQS Fifo being too slow, it's bee a long time since I checked FIFO throughput. Checking now, 3000msg/sec is a lot higher than it was, so probably not a concern any longer, but i'd like to focus on Kinesis. Yes, we have run soak tests through Kinesis and we're very happy with throughput.
Regarding "shard will be blocked" comment - Of course, not the shard itself, i meant the consumer will not be able to continue receiving new batches.
You mention "So in the Kinesis world, if you want to maintain ordering you can only have a single consumer on the stream (shard, really)." this is not what i understand? If multiple consumers are reading from a single shard, they are all receiving the same data completely independantly from other consumers, but the shard guarantees order, so they all get ordered data?
Finally, I have reached out to AWS locally - it's just taking some time and i was looking to expedite.
Cheers