Kafka vs RabbitMQ vs SQS: how to choose for an event-driven system

we're designing a new event-driven service that needs to process about 10k messages per second, requiring at-least-once delivery, and the ability to replay historical events. we'll have around 5 consumers on the same topic group. i'm trying to decide between kafka, rabbitmq, and sqs. kafka seems like the go-to for replays and throughput, but the operational overhead is a concern for a smaller team. rabbitmq is simpler to manage but i'm not sure about its replay story for high volumes. sqs is fully managed, which is tempting, but its replay capabilities are more limited to dead-letter queues, not full topic history. what are the key decision points here? how do you balance operational simplicity with features like replay and high throughput for this kind of workload?