Question

A DevOps team needs to forward specific EC2 state-change events to a third-party incident management SaaS platform via its REST API. The SaaS API requires an OAuth client-credentials token in the Authorization header and enforces a strict limit of 10 requests per second. During large-scale Auto Scaling events, hundreds of EC2 state-change events can be generated in a short burst, and the team is seeing HTTP 429 throttling errors and dropped notifications. Which approach best delivers these events reliably while respecting the API rate limit and handling authentication automatically?

Accepted Answer

Create an EventBridge API destination with a connection configured for OAuth client-credentials authorization, set the invocation rate limit per second on the API destination, and attach a dead-letter queue to the target for failed deliveries.

Answer

Configure an EventBridge rule targeting a Lambda function that stores the OAuth token in environment variables and calls the SaaS API directly, retrying on 429 responses with exponential backoff in code.

Answer

Send events to an SNS topic with an HTTPS subscription pointing at the SaaS API endpoint, and use SNS delivery retry policies to smooth out the request rate.

Answer

Create an EventBridge rule that targets an SQS FIFO queue, then have the SaaS platform poll the queue to retrieve events at its own pace.