How should a solutions architect accomplish this?
Create an Amazon Simple Queue Service (Amazon SQS) FIFO queue to hold messages. Set up an AWS Lambda function to process messages from the queue.
Create an Amazon Simple Notification Service (Amazon SNS) topic to deliver notifications containing payloads to process. Configure an AWS Lambda function as a subscriber.
Create an Amazon Simple Queue Service (Amazon SQS) standard queue to hold messages. Set up an AWS Lambda function to process messages from the queue independently.
Create an Amazon Simple Notification Service (Amazon SNS) topic to deliver notifications containing payloads to process. Configure an Amazon Simple Queue Service (Amazon SQS) queue as a subscriber.
Explanations:
An Amazon SQS FIFO queue preserves the order of messages and ensures exactly-once processing. Using an AWS Lambda function to process the messages allows for automated handling of the event data with minimal operational overhead, fulfilling the requirement to maintain order.
Amazon SNS is used for pub/sub messaging and does not guarantee message order. Therefore, using SNS to deliver notifications would not preserve the specific order of event data, which is crucial for this scenario.
An Amazon SQS standard queue does not guarantee the order of messages and allows for at-least-once delivery, meaning that it can potentially process messages out of order. This does not meet the requirement to maintain the specific order of event data.
While SNS can push messages to an SQS queue, using an SNS topic does not guarantee the order of the messages in the queue itself, as it is a standard queue. This solution fails to maintain the required order of processing.
As far as I’m aware, the answer is:
Create an Amazon Simple Queue Service (Amazon SQS) FIFO queue to hold messages. Set up an AWS Lambda function to process messages from the queue.