A social media company runs a rewards website that gives users points for uploading videos. Partners verify user eligibility using a unique user ID, and partners want to receive user IDs via an HTTP endpoint whenever the company awards points. Hundreds of vendors sign up daily. The company needs a scalable architecture that lets the website add partners quickly with the LEAST implementation effort. Which solution meets these requirements?

The correct answer is to use Amazon SNS with HTTP(S) endpoints. SNS is a highly scalable, fully managed messaging service that supports fan-out messaging. Partners can subscribe to the SNS topic using their HTTP endpoints, and when the company publishes user IDs to the topic, SNS automatically delivers the messages to all subscribed partners. This approach requires minimal implementation effort for new partners, as they only need to subscribe their existing HTTP endpoint. Incorrect options: Amazon Timestream is a time-series database, not ideal for managing a list of partners or orchestrating notifications. A Lambda function would still be needed to iterate through partners, which adds complexity. AWS Step Functions would require creating a new task for every partner, making it cumbersome and high effort to add new partners daily. Amazon Kinesis Data Streams is designed for real-time data ingestion and processing, not for fan-out notifications to HTTP endpoints. It would require building custom producer and consumer applications to manage partner lists and send notifications, which is more complex than SNS.