Amazon MQ

Name: Amazon MQ API
Brand: Amazon MQ
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkinghmac22 EndpointsREST

For Agents

Provision and operate managed ActiveMQ and RabbitMQ message brokers — create brokers, manage broker users, apply versioned configurations, and reboot for maintenance.

Quickstart

Get started with Amazon MQ in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an Amazon MQ broker"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon MQ API.

Provision an ActiveMQ or RabbitMQ broker with engine version, instance type, deployment mode, and subnet placement

Apply a versioned XML configuration to a broker and roll forward to new revisions for parameter changes

Create, update, and delete broker users with per-user passwords and group memberships

List and describe broker instances, configurations, and configuration revisions across an account

GET STARTED

Start building with Amazon MQ API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon MQ, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon MQ, keeping it validated and agent-ready. Amazon MQ is the managed message-broker service for Apache ActiveMQ and RabbitMQ — it provisions broker instances, manages users and access, applies versioned configurations, schedules maintenance reboots and tags brokers for cost tracking. The 22 endpoints cover the full broker lifecycle: CreateBroker through DeleteBroker, ListConfigurations and ListConfigurationRevisions, CreateUser/UpdateUser/DeleteUser per broker, RebootBroker for in-place restarts, and tag management.

Use Cases

Patterns agents use Amazon MQ API for, with concrete tasks.

★ Provision Managed Brokers for Legacy JMS Workloads

Teams migrating JMS or AMQP workloads to AWS need a managed broker rather than self-hosted ActiveMQ on EC2. Amazon MQ's CreateBroker provisions an ActiveMQ or RabbitMQ instance with a chosen engine version, deployment mode (single-instance or active/standby), instance type and VPC subnet layout. The service handles patching, backups and failover so an agent can stand up a working broker in a single API call rather than building Chef recipes.

Call POST /v1/brokers with EngineType=ACTIVEMQ, EngineVersion=5.17.6, HostInstanceType=mq.m5.large, DeploymentMode=ACTIVE_STANDBY_MULTI_AZ and a Users array, then poll DescribeBroker until BrokerState=RUNNING

Manage Broker Users Without Touching the Broker Console

Producers and consumers of a broker need credentials managed centrally. The Amazon MQ Users sub-API lets an agent create, update and delete users with per-user groups and console access flags. Changes are applied without rebooting the broker for ActiveMQ in most cases, and pending changes can be flushed by an explicit RebootBroker. This avoids logging into the broker web console to maintain credentials.

Call PUT /v1/brokers/{broker-id}/users/{username} with a Password and Groups array, then RebootBroker if the change requires a restart

Roll Out Versioned Broker Configurations

Operations teams need to manage broker XML configuration as code — destination policies, network connectors, ACLs — and roll forward changes safely. Amazon MQ's Configurations API stores versioned XML revisions, and brokers can be pinned to a specific revision via UpdateBroker. An agent can author a new revision, validate it through the API and pin a broker to the new revision during a maintenance window.

Call POST /v1/configurations/{configuration-id}/revisions with a base64-encoded ActiveMQ XML, then UpdateBroker with the configuration revision id

AI Agent Integration for Broker Operations

Through Jentic, an agent can manage Amazon MQ brokers from natural-language intents — provision, list, configure, reboot — without browsing the AWS console. Jentic returns the input schema for each MQ operation and brokers SigV4 credentials, so on-call automation around broker maintenance can be expressed as LLM tool calls rather than scripted with boto3.

Resolve the intent 'provision an ActiveMQ broker' via Jentic search, load the CreateBroker schema, and execute it with engine type, version, host instance type and subnet IDs

Key Endpoints

22 endpoints — jentic publishes the only available openapi specification for amazon mq, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/brokers

Create a new broker (ActiveMQ or RabbitMQ)

GET

/v1/brokers

List all brokers in the account

GET

/v1/brokers/{broker-id}

Describe a broker's configuration and state

POST

/v1/brokers/{broker-id}/reboot

Reboot a broker to apply changes

PUT

/v1/brokers/{broker-id}/users/{username}

Create or update a broker user

POST

/v1/configurations

Create a new broker configuration

POST

/v1/tags/{resource-arn}

Tag a broker or configuration

POST

/v1/brokers

Create a new broker (ActiveMQ or RabbitMQ)

GET

/v1/brokers

List all brokers in the account

GET

/v1/brokers/{broker-id}

Describe a broker's configuration and state

POST

/v1/brokers/{broker-id}/reboot

Reboot a broker to apply changes

PUT

/v1/brokers/{broker-id}/users/{username}

Create or update a broker user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys are stored encrypted in the Jentic MAXsystem vault. Jentic signs each Amazon MQ control-plane request with SigV4 on the agent's behalf — broker user passwords managed via the Users sub-API are also handled through Jentic without exposing them in the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create an Amazon MQ broker') and Jentic returns the matching MQ operation with its input schema, so the agent can call CreateBroker, RebootBroker or UpdateUser without browsing the AWS docs.

Time to first call

Direct Amazon MQ integration: 1-3 days for IAM scoping, broker provisioning polling and configuration revision plumbing. Through Jentic: a few hours — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon EventBridge

EventBridge is AWS's serverless event bus — useful when you want managed routing rather than a JMS or AMQP broker

Choose EventBridge for cloud-native event routing with no broker maintenance. Use Amazon MQ when an existing application speaks JMS, MQTT or AMQP and cannot easily switch protocols.

Complementary

Amazon EC2

EC2 hosts the producer and consumer applications that connect to Amazon MQ brokers

Use to provision the compute that talks to a broker, especially when fine-grained network controls and security groups are needed.

Complementary

Amazon CloudWatch Logs

CloudWatch Logs receives broker general and audit logs for a configured broker

Use when an agent needs to query broker logs for connection failures, slow consumers or auth issues.

FAQs

Specific to using Amazon MQ API through Jentic.

Why is there no official OpenAPI spec for Amazon MQ?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon MQ via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon MQ API use?

The Amazon MQ control plane is signed with AWS SigV4 using IAM access keys; the broker data plane (publishing and consuming messages) uses broker-managed username/password credentials separately. Through Jentic, AWS credentials are stored in the MAXsystem vault and used to sign each MQ control-plane call on the agent's behalf.

Can I create both ActiveMQ and RabbitMQ brokers with the same API?

Yes. POST /v1/brokers accepts an EngineType of ACTIVEMQ or RABBITMQ, with engine-specific options for EngineVersion and HostInstanceType. Configuration revisions and the Users sub-resource behave slightly differently between engines, so check the returned BrokerEngineType before applying engine-specific calls.

What are the rate limits for the Amazon MQ API?

AWS applies per-account control-plane throttling to Amazon MQ; specific TPS limits are not published in the spec. Treat throttling as expected and use exponential backoff. Broker provisioning itself takes minutes, so poll DescribeBroker rather than retrying CreateBroker.

How do I provision a broker through Jentic?

Use the Jentic search query 'provision an ActiveMQ broker', load the operation behind POST /v1/brokers, and execute it with EngineType, EngineVersion, HostInstanceType, DeploymentMode, SubnetIds and an initial Users array. Jentic signs the request with SigV4 against your stored AWS credentials.

Do I need to reboot a broker after updating a user?

Most ActiveMQ user updates apply on a maintenance schedule; pending changes can be applied immediately by calling POST /v1/brokers/{broker-id}/reboot. RabbitMQ user changes typically take effect without a reboot. Always check the broker's pending change set in DescribeBroker before triggering a reboot.