Amazon MQ
Amazon MQ is a managed message broker service for Apache ActiveMQ and RabbitMQ that makes it easy to set up and operate message brokers in the cloud, enabling you to migrate to a message broker without writing the code that typically enables interoperability with existing applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amazon MQ the way a machine reads it — 260 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon MQ scores 47.5/100 (developing), with a separate agent-readiness read of 37/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Amazon MQ's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amazon-mq/"
title="Amazon MQ on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amazon-mq.svg"
alt="Amazon MQ Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/amazon-mq/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amazon-mq/"
title="Amazon MQ on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amazon-mq/card.svg"
alt="Amazon MQ Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Amazon MQ
Each block below is one kind of artifact we hold for Amazon MQ. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon MQ Broker Engine Types API
The Broker Engine Types API from Amazon MQ — 1 operation(s) for broker engine types.
Amazon MQ Broker Instance Options API
The Broker Instance Options API from Amazon MQ — 1 operation(s) for broker instance options.
Amazon MQ Brokers API
The Brokers API from Amazon MQ — 5 operation(s) for brokers.
Amazon MQ Configurations API
The Configurations API from Amazon MQ — 4 operation(s) for configurations.
Amazon MQ Tags API
The Tags API from Amazon MQ — 2 operation(s) for tags.
Postman Collections 5
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAmazonMQ Broker Engine Types API
OPEN COLLECTIONAmazonMQ Broker Engine Types Broker Instance Options API
OPEN COLLECTIONAmazonMQ Broker Engine Types Brokers API
OPEN COLLECTIONAmazonMQ Broker Engine Types Configurations API
OPEN COLLECTIONAmazonMQ Broker Engine Types Tags API
OPEN COLLECTIONAmazon MQ API
OPEN COLLECTIONScroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Mq Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Mq Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Managed Message Brokers
Fully managed Apache ActiveMQ and RabbitMQ brokers with automated provisioning and maintenance.
Protocol Support
Supports AMQP, MQTT, OpenWire, STOMP, and WebSocket protocols for broad compatibility.
High Availability
Active/standby configurations with automatic failover for high availability.
Network of Brokers
Create networks of brokers for distributed messaging across regions and availability zones.
Broker Management API
Programmatically create, configure, and manage brokers and configurations.
Security
Encryption at rest and in transit, VPC isolation, and IAM integration.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Mq Mq Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon MQ API Rules
SPECTRALAmazon MQ API Rules
SPECTRALJSON Schema 74
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ActionRequired
JSON SCHEMAAuthenticationStrategy
JSON SCHEMAAvailabilityZone
JSON SCHEMABrokerEngineType
JSON SCHEMABrokerInstanceOption
JSON SCHEMABrokerInstance
JSON SCHEMABrokerState
JSON SCHEMABrokerStorageType
JSON SCHEMABrokerSummary
JSON SCHEMAChangeType
JSON SCHEMAConfigurationId
JSON SCHEMAConfigurationRevision
JSON SCHEMAConfiguration
JSON SCHEMAConfigurations
JSON SCHEMACreateBrokerRequest
JSON SCHEMACreateBrokerResponse
JSON SCHEMACreateConfigurationRequest
JSON SCHEMACreateConfigurationResponse
JSON SCHEMACreateTagsRequest
JSON SCHEMACreateUserRequest
JSON SCHEMACreateUserResponse
JSON SCHEMADayOfWeek
JSON SCHEMADeleteBrokerRequest
JSON SCHEMADeleteBrokerResponse
JSON SCHEMADeleteTagsRequest
JSON SCHEMADeleteUserRequest
JSON SCHEMADeleteUserResponse
JSON SCHEMADeploymentMode
JSON SCHEMADescribeBrokerEngineTypesRequest
JSON SCHEMADescribeBrokerEngineTypesResponse
JSON SCHEMADescribeBrokerInstanceOptionsRequest
JSON SCHEMADescribeBrokerInstanceOptionsResponse
JSON SCHEMADescribeBrokerRequest
JSON SCHEMADescribeBrokerResponse
JSON SCHEMADescribeConfigurationRequest
JSON SCHEMADescribeConfigurationResponse
JSON SCHEMADescribeConfigurationRevisionRequest
JSON SCHEMADescribeConfigurationRevisionResponse
JSON SCHEMADescribeUserRequest
JSON SCHEMADescribeUserResponse
JSON SCHEMAEncryptionOptions
JSON SCHEMAEngineType
JSON SCHEMAEngineVersion
JSON SCHEMALdapServerMetadataInput
JSON SCHEMALdapServerMetadataOutput
JSON SCHEMAListBrokersRequest
JSON SCHEMAListBrokersResponse
JSON SCHEMAListConfigurationRevisionsRequest
JSON SCHEMAListConfigurationRevisionsResponse
JSON SCHEMAListConfigurationsRequest
JSON SCHEMAListConfigurationsResponse
JSON SCHEMAListTagsRequest
JSON SCHEMAListTagsResponse
JSON SCHEMAListUsersRequest
JSON SCHEMAListUsersResponse
JSON SCHEMALogs
JSON SCHEMALogsSummary
JSON SCHEMAMaxResults
JSON SCHEMAPendingLogs
JSON SCHEMARebootBrokerRequest
JSON SCHEMARebootBrokerResponse
JSON SCHEMASanitizationWarningReason
JSON SCHEMASanitizationWarning
JSON SCHEMAUnauthorizedException
JSON SCHEMAUpdateBrokerRequest
JSON SCHEMAUpdateBrokerResponse
JSON SCHEMAUpdateConfigurationRequest
JSON SCHEMAUpdateConfigurationResponse
JSON SCHEMAUpdateUserRequest
JSON SCHEMAUpdateUserResponse
JSON SCHEMAUserPendingChanges
JSON SCHEMAUser
JSON SCHEMAUserSummary
JSON SCHEMAWeeklyStartTime
JSON SCHEMAScroll within the panel for all 74 ·
JSON Structure 74
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Mq Api Action Required Structure
JSON STRUCTUREMq Api Authentication Strategy Structure
JSON STRUCTUREMq Api Availability Zone Structure
JSON STRUCTUREMq Api Broker Engine Type Structure
JSON STRUCTUREMq Api Broker Instance Option Structure
JSON STRUCTUREMq Api Broker Instance Structure
JSON STRUCTUREMq Api Broker State Structure
JSON STRUCTUREMq Api Broker Storage Type Structure
JSON STRUCTUREMq Api Broker Summary Structure
JSON STRUCTUREMq Api Change Type Structure
JSON STRUCTUREMq Api Configuration Id Structure
JSON STRUCTUREMq Api Configuration Revision Structure
JSON STRUCTUREMq Api Configuration Structure
JSON STRUCTUREMq Api Configurations Structure
JSON STRUCTUREMq Api Create Broker Request Structure
JSON STRUCTUREMq Api Create Broker Response Structure
JSON STRUCTUREMq Api Create Configuration Request Structure
JSON STRUCTUREMq Api Create Configuration Response Structure
JSON STRUCTUREMq Api Create Tags Request Structure
JSON STRUCTUREMq Api Create User Request Structure
JSON STRUCTUREMq Api Create User Response Structure
JSON STRUCTUREMq Api Day Of Week Structure
JSON STRUCTUREMq Api Delete Broker Request Structure
JSON STRUCTUREMq Api Delete Broker Response Structure
JSON STRUCTUREMq Api Delete Tags Request Structure
JSON STRUCTUREMq Api Delete User Request Structure
JSON STRUCTUREMq Api Delete User Response Structure
JSON STRUCTUREMq Api Deployment Mode Structure
JSON STRUCTUREMq Api Describe Broker Engine Types Request Structure
JSON STRUCTUREMq Api Describe Broker Engine Types Response Structure
JSON STRUCTUREMq Api Describe Broker Request Structure
JSON STRUCTUREMq Api Describe Broker Response Structure
JSON STRUCTUREMq Api Describe Configuration Request Structure
JSON STRUCTUREMq Api Describe Configuration Response Structure
JSON STRUCTUREMq Api Describe Configuration Revision Request Structure
JSON STRUCTUREMq Api Describe User Request Structure
JSON STRUCTUREMq Api Describe User Response Structure
JSON STRUCTUREMq Api Encryption Options Structure
JSON STRUCTUREMq Api Engine Type Structure
JSON STRUCTUREMq Api Engine Version Structure
JSON STRUCTUREMq Api Ldap Server Metadata Input Structure
JSON STRUCTUREMq Api Ldap Server Metadata Output Structure
JSON STRUCTUREMq Api List Brokers Request Structure
JSON STRUCTUREMq Api List Brokers Response Structure
JSON STRUCTUREMq Api List Configuration Revisions Request Structure
JSON STRUCTUREMq Api List Configuration Revisions Response Structure
JSON STRUCTUREMq Api List Configurations Request Structure
JSON STRUCTUREMq Api List Configurations Response Structure
JSON STRUCTUREMq Api List Tags Request Structure
JSON STRUCTUREMq Api List Tags Response Structure
JSON STRUCTUREMq Api List Users Request Structure
JSON STRUCTUREMq Api List Users Response Structure
JSON STRUCTUREMq Api Logs Structure
JSON STRUCTUREMq Api Logs Summary Structure
JSON STRUCTUREMq Api Max Results Structure
JSON STRUCTUREMq Api Pending Logs Structure
JSON STRUCTUREMq Api Reboot Broker Request Structure
JSON STRUCTUREMq Api Reboot Broker Response Structure
JSON STRUCTUREMq Api Sanitization Warning Reason Structure
JSON STRUCTUREMq Api Sanitization Warning Structure
JSON STRUCTUREMq Api Unauthorized Exception Structure
JSON STRUCTUREMq Api Update Broker Request Structure
JSON STRUCTUREMq Api Update Broker Response Structure
JSON STRUCTUREMq Api Update Configuration Request Structure
JSON STRUCTUREMq Api Update Configuration Response Structure
JSON STRUCTUREMq Api Update User Request Structure
JSON STRUCTUREMq Api Update User Response Structure
JSON STRUCTUREMq Api User Pending Changes Structure
JSON STRUCTUREMq Api User Structure
JSON STRUCTUREMq Api User Summary Structure
JSON STRUCTUREMq Api Weekly Start Time Structure
JSON STRUCTUREScroll within the panel for all 74 ·
Examples 74
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Mq Api Broker State Example
EXAMPLEMq Api Change Type Example
EXAMPLEMq Api Configuration Example
EXAMPLEMq Api Day Of Week Example
EXAMPLEMq Api Engine Type Example
EXAMPLEMq Api Logs Example
EXAMPLEMq Api Logs Summary Example
EXAMPLEMq Api Max Results Example
EXAMPLEMq Api Pending Logs Example
EXAMPLEMq Api User Example
EXAMPLEMq Api User Summary Example
EXAMPLEScroll within the panel for all 74 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Application Migration
Migrate on-premises ActiveMQ or RabbitMQ workloads to AWS without code changes.
Microservices Decoupling
Use message queues to decouple microservices for improved reliability and scalability.
Enterprise Integration
Connect enterprise applications using standard messaging protocols.
Event-Driven Architecture
Build event-driven applications with reliable message delivery.
Resources
Every other property we hold for Amazon MQ — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-mq · machine-readable index on apis.io
This is an independent, third-party profile of Amazon MQ, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.