Exam AWS Certified SysOps Administrator - Associate topic 1 question 280 discussion

EventBridge Rule with API Destinations: EventBridge allows you to create rules that match certain events (in this case, CloudWatch alarms) and forward them to specified targets. API Destinations are one such target, which allows you to directly send the events to an HTTPS endpoint, such as the ticketing system. No Additional Services: Option A involves setting up an EventBridge rule and using the API Destinations feature, which means there are no additional services like Kinesis, Lambda, or Step Functions to configure and manage. This simplifies the solution and reduces development time. Input Transformer: The input transformer in the EventBridge rule allows you to convert the source data (CloudWatch alarm event) into the required JSON format for the ticketing system. This makes it easy to transform the data without the need for additional AWS Glue jobs or complex transformations.

EventBridge to SNS to HTTPS

Come on people, how can you select C>>>>SNS can not transform events.

Probably would go with C (SNS option as target due to LEAST effort required). For option A, it would still need to convert the format that leads to more Development time which is what a more primary focus in this question!

Answer is A as SNS can't do the conversion to json..

https://aws.amazon.com/blogs/compute/using-api-destinations-with-amazon-eventbridge/ API eventbridge can integrate with automation ticket. example: https://aws.amazon.com/blogs/compute/using-api-destinations-with-amazon-eventbridge/#:~:text=When%20you%20create%20a%20rule%20to%20route%20to%20this%20API%20destination%2C%20use%20the%20Input%20transformer%20to%20build%20the%20defined%20JSON%20payload%2C%20as%20shown%20in%20the%20previous%20Datadog%20example.%20When%20an%20event%20matches%20the%20rule%2C%20EventBridge%20calls%20the%20Zendesk%20Create%20Ticket%20API.%20The%20new%20ticket%20appears%20in%20the%20Zendesk%20dashboard%3A

https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-transform-target-input.html#eb-transform-input-examples

I belive that answer is A simply because with C, SNS does not allow any kind of transformation feature that would convert JSON. So that would entail more development requirements to overcome. A sounds like more steps but it seems like the only fully integrated answer.

Option C requires the LEAST development time, it leverages Amazon SNS message to eliminate the need to write custom code or uttilize additional services like AWS Lambda or AWS Glue for data transformation. Option A would require more time because it would require custom code to change the events from CloudWatch alarms into the required JSON format. It will also would require you to configure the ticketing system to accept requests from Amazon EventBridge.

While I'm not an expert on this, SNS seems like the simplest option and it works for this. "You can use Amazon SNS to send notification messages to one or more HTTP or HTTPS endpoints. When you subscribe an endpoint to a topic, you can publish a notification to the topic and Amazon SNS sends an HTTP POST request delivering the contents of the notification to the subscribed endpoint." https://docs.aws.amazon.com/sns/latest/dg/sns-http-https-endpoint-as-subscriber.html