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 ensures that messages are processed in the order they are received, which meets the requirement of maintaining order. Using AWS Lambda for processing minimizes operational overhead, as Lambda automatically scales and manages infrastructure.
Amazon SNS is not designed to maintain the order of messages. It delivers notifications to subscribers, but does not ensure that messages are processed in a specific order, which is a key requirement of the scenario.
An Amazon SQS standard queue does not guarantee the order of message processing. This fails to meet the requirement of maintaining the specific order of the event data during processing.
While an SNS topic can deliver messages, it does not guarantee order. Using an SQS queue as a subscriber to SNS will not preserve the order of messages, which is essential in this scenario.
I measure that 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.