An insurer is moving its claims system to AWS. The system's components exchange messages through an on-premises Apache ActiveMQ broker using JMS, and the team wants to migrate without rewriting that messaging code. Which service fits?
Choose an answer to check it. Afterward, select any option to review its explanation.
Amazon MQ is the managed broker AWS recommends for migrating applications that depend on existing broker APIs such as JMS and on engines like ActiveMQ, so the components can keep their messaging code.
SNS is a managed publish-subscribe service, so it fits the idea of messaging. It delivers through topics to endpoints such as queues, functions and email, not as a JMS broker, so the existing code would still have to change.
SQS is AWS's queue for decoupling components and is recommended for new applications, so it is a natural first thought. Using it means moving the components onto its own web services API, which is the rewrite the team wants to avoid.
AWS Batch also manages work queues, which can make it sound related. It provisions compute for submitted batch jobs and does not provide a message broker for application components.
id q1a1173a9ad