A company’s order system sends requests from clients to Amazon EC2 instances that process orders and store them in Amazon RDS. Users must currently reprocess orders when the system fails. The company wants a resilient solution that will automatically process orders after an outage. What should a solutions architect do to meet these requirements?

The correct solution uses Amazon SQS to decouple the order system from the EC2 instances, providing resilience. When the order system sends messages to an SQS queue, these messages are durably stored even if the EC2 instances are unavailable. The Auto Scaling group ensures that healthy EC2 instances are always running to process messages from the queue. If an instance fails, another takes its place, and messages remain in the queue until processed, preventing data loss and ensuring automatic reprocessing. Moving EC2 instances into an Auto Scaling group behind an ALB provides high availability but doesn't solve the reprocessing requirement for orders that were in flight during a failure. The EventBridge/ECS option is not directly applicable here as EventBridge is typically for event-driven architectures, not for durable message queuing for order processing. The SNS/Lambda/Run Command option is overly complex and doesn't offer the durable message storage and automatic retry mechanism of SQS for order processing.