A migrated application sends shipping requests that must be processed in order, without duplicates. Requests are up to 250 KB and take 5–10 minutes to process. The current system produces duplicate, lost, or out-of-order requests. How should a developer rearchitect the solution to guarantee ordered, non-duplicated processing?

The correct solution uses an Amazon SQS FIFO (First-In, First-Out) queue because it guarantees message ordering and exactly-once processing, which prevents duplicates. The Lambda function processes requests from the queue. SQS FIFO queues are ideal for scenarios requiring strict message order and preventing duplicates, aligning perfectly with the problem statement. Incorrect options: Kinesis Data Firehose and Kinesis Data Streams are primarily for real-time data streaming and analytics, not for guaranteed ordered, non-duplicated processing of individual requests that take minutes to process. Amazon SNS topics do not guarantee message order or prevent duplicates, making them unsuitable for this requirement. Amazon SQS standard queues do not guarantee message order and may deliver duplicates, failing to meet the core requirements of the problem.