A mobile application is deployed on Amazon EC2 instances with Amazon EC2 Auto Scaling for efficient capacity management.
Amazon EventBridge rules are created to send Amazon EC2 Auto Scaling generated events for terminated instances to Amazon SNS as a target.
Junior Sysops administrator observes many events are not successfully delivered to Amazon SNS and are dropped.
He is looking for your suggestion for retaining these failed events instead of getting dropped. Which of the following configurations in Amazon EventBridge can be done to meet this requirement?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C.
When an event is not delivered to the target, after retry time, Amazon EventBridge drops these events & does not process them further.
To avoid getting events dropped, EventBridge DLQs can be created to store all failed delivery events which can be analyzed and processed later.
EventBridge DLQs are standard Amazon SQS queues.
FIFO Amazon SQS queues are not supported.
Option A is incorrect as new EventBridge rules are not required to be created for dropped events.
Option B is incorrect as EventBridge rules can be created for inter-region events, no need to have separate EventBridge rules per region.
Option D is incorrect as FIFO queues are not supported as EventBridge DLQ.
For more information on using EventBridge DLQs with Amazon EventBridge, refer to the following URL,
https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-rule-dlq.htmlSure, I'd be happy to explain the answer to this question in detail!
The scenario described in the question involves a mobile application deployed on Amazon EC2 instances using Amazon EC2 Auto Scaling for efficient capacity management. In this setup, Amazon EventBridge rules are created to send events generated by Amazon EC2 Auto Scaling for terminated instances to Amazon SNS as a target. However, the junior Sysops administrator has observed that many of these events are not successfully delivered to Amazon SNS and are getting dropped. The question asks for a suggestion on how to retain these failed events instead of dropping them.
Option A: Configure new EventBridge rules for events that are getting dropped. This option suggests creating new EventBridge rules for events that are getting dropped. However, this option does not provide any solution for retaining the failed events, it only creates new rules for the same events that are currently getting dropped.
Option B: Configure new EventBridge rules for these events in each region as all inter region events are getting dropped. This option suggests creating new EventBridge rules for inter-region events that are getting dropped. However, this option does not provide any solution for retaining the failed events, it only creates new rules for the same events that are currently getting dropped.
Option C: Configure an EventBridge DLQ as standard Amazon SQS queues & send all failed events to it for further processing. This option suggests configuring an EventBridge Dead Letter Queue (DLQ) as a standard Amazon SQS queue and sending all failed events to it for further processing. A DLQ is a queue that receives messages that could not be delivered to their intended destination. In this case, failed events that are not successfully delivered to Amazon SNS would be sent to the DLQ instead. This option provides a solution for retaining failed events and allowing for further processing.
Option D: Configure an EventBridge DLQ as FIFO Amazon SQS queues & send all failed events to it for further processing. This option suggests configuring an EventBridge Dead Letter Queue (DLQ) as a FIFO Amazon SQS queue and sending all failed events to it for further processing. A FIFO queue is a special type of Amazon SQS queue that guarantees that messages are processed in the order in which they are sent. However, using a FIFO queue may not be necessary in this scenario, as the order of the failed events may not be important. Option C, which suggests using a standard Amazon SQS queue as a DLQ, would be a simpler and more cost-effective solution.
In conclusion, the best option for retaining failed events that are not successfully delivered to Amazon SNS in this scenario would be to configure an EventBridge DLQ as a standard Amazon SQS queue and send all failed events to it for further processing (Option C).