A company is building a new application that uses multiple serverless architecture components. The application architecture includes an Amazon API Gateway REST API and AWS Lambda functions to manage i

While Amazon SNS with message filtering can meet the requirements, in scenarios implying large-scale streaming or replayability needs, MSK offers more robust streaming capabilities, potentially making it the 'least operational overhead' for those specific contexts.

Using Amazon EC2 instances introduces significant operational overhead for managing the instances and implementing custom messaging and filtering logic, which contradicts the 'least operational overhead' and serverless requirements.

Amazon Managed Streaming for Apache Kafka (MSK) provides a durable, high-throughput streaming platform suitable for multiple consumers (Lambda functions) and complex data processing, where filtering can be achieved by consumers subscribing to specific topics/partitions or implementing filtering logic, offering managed 'serverless' operations for the Kafka brokers.

Sending requests to multiple Amazon SQS queues would increase management overhead, and SQS lacks native message filtering capabilities at the subscription level as robustly as SNS or EventBridge.