---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Amazon MQ Broker

# Amazon MQ Broker pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated May 13, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Amazon MQ Broker pattern-based discovery

The Amazon MQ Broker pattern-based discovery enables ServiceNow customers to automatically discover and map Amazon MQ Brokers within their AWS cloud environments.
This functionality is provided through the Discovery and Service Mapping Patterns application, which updates and populates data about MQ Brokers into both CMDB and non-CMDB tables.
Ensuring the latest version of the Discovery and Service Mapping Patterns application is installed is essential to effectively discover these resources.
Show full answer Show less  

## Key Features

* **Prerequisites and Configuration:** Customers must verify AWS discovery prerequisites, remove any relevant resources from the Resource Inclusion List to avoid duplicate discovery, and enable the Amazon MQ Broker pattern, which is disabled by default.
* **GovCloud Support:** Discovering AWS GovCloud (US) accounts requires configuring the discovery schedule with a datacenter URL specific to GovCloud.
* **Data Population:** The discovery process populates detailed Amazon MQ Broker data into both CMDB and non-CMDB tables using the *Amazon AWS - MQ Broker - Extended Inventory (LP)* pattern.
* **CMDB Tables:** The `cmdbcicloudmessagingservice` table stores key broker information such as name, ARN, resource type, install status, and operational status.
* **Non-CMDB Tables:** The `cmdbawsmqbroker` table contains broker-specific details including broker ID, state, engine type and version, host instance type, and references back to the CMDB cloud messaging service record.
* **CI Relationships and References:** The pattern establishes relationships such as "Hosted on" between Cloud Messaging Service CIs and AWS Datacenter CIs, supporting comprehensive mapping in the CMDB.
* **AWS Tag Discovery:** Tags associated with MQ Brokers are collected and stored in the `cmdbkeyvalue` table, linked to the Cloud Messaging Service configuration items for enhanced resource categorization.

## Practical Benefits for ServiceNow Customers

By leveraging this pattern-based discovery, ServiceNow customers can maintain an accurate, up-to-date inventory of their Amazon MQ Brokers within their CMDB. This improves visibility into broker configurations, operational status, and relationships with AWS datacenters, supporting better cloud resource management, impact analysis, and operational decision-making. Tag collection further enhances the ability to organize and filter discovered resources according to business or technical metadata.  
Discovery and Service Mapping Patterns finds Amazon MQ Brokers on your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Pattern-based discovery and mapping requirements {#aws-mq-broker__section_rpj_fj2_bgc}

Verify the AWS discovery prerequisites
:   For more information, see the prerequisites section in [AWS discovery using patterns](https://www.servicenow.com/docs/NFaTlkGaSxMWb2bQPsCnCA "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Remove resources from the Resource Inclusion List table
:   Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource
    Inclusion List, see [AWS Resource Inventory discovery with Patterns](https://www.servicenow.com/docs/0pDNq0441mpy~sExfQvvqA "The ServiceNow Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Enable the relevant pattern
:   The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#aws-mq-broker__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud
:   Discovering AWS GovCloud (US) accounts requires using a datacenter URL when setting up an AWS service account. For more information, see [Create AWS service accounts](https://www.servicenow.com/docs/vpueuFRHMWLNi6dzsJv94A "Create AWS service accounts on the ServiceNow AI Platform to access your AWS account during AWS discovery.").
Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

## Data stored in non-CMDB tables {#aws-mq-broker__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Amazon AWS - MQ Broker - Extended Inventory (LP) pattern.

You can review the non-CMDB
AWS tables by navigating to AllConfigurationAWS. You can also search the navigation filter for the specific pattern name.  
{#aws-mq-broker__table_non_cmdb__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the broker. |
| Object ID \[object_id\] | The Amazon Resource Name (ARN) of the broker. |
| Broker Id \[broker_id\] | The unique ID of the broker. |
| Broker State \[broker_state\] | The current state of the broker. For example: RUNNING, CREATION_IN_PROGRESS, DELETION_IN_PROGRESS, or REBOOT_IN_PROGRESS. |
| Engine Type \[engine_type\] | The type of broker engine. For example: ACTIVEMQ or RABBITMQ. |
| Engine Version \[engine_version\] | The version of the broker engine. |
| Host Instance Type \[host_instance_type\] | The broker's instance type, which determines the computing resources assigned to the broker. |
| Configuration Item \[configuration_item\] | References the Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] table. |
[Table 1. AWS MQ Broker \[cmdb_aws_mq_broker\]]

{#aws-mq-broker__table_non_cmdb}

## Data stored in CMDB tables {#aws-mq-broker__section_ggp_ql2_bgc}

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - MQ Broker - Extended Inventory (LP) pattern.  
{#aws-mq-broker__table_cmdb__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the broker. |
| Object ID \[object_id\] | The ARN of the broker. |
| Type \[type\] | Type of resource. The value is set to AWS::MQ::Broker. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
[Table 2. Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\]]

{#aws-mq-broker__table_cmdb}

## CI relationships {#aws-mq-broker__section_dc4_ghc_dgc}

The Amazon AWS - MQ Broker - Extended Inventory (LP) pattern creates the following relationships and references to support Amazon MQ Broker discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table.  
{#aws-mq-broker__table_relationships__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] |
[Table 3. CI relationships]

{#aws-mq-broker__table_relationships}  
{#aws-mq-broker__table_ci_references__entry__3}

| CI | Field | Referenced CI |
|-|-|-|
| AWS MQ Broker \[cmdb_aws_mq_broker\] | Configuration Item \[configuration_item\] | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] |
| Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] |
[Table 4. CI references]

{#aws-mq-broker__table_ci_references}

## AWS Tag discovery {#aws-mq-broker__section_lyw_zhc_dgc}

The Amazon AWS - MQ Broker - Extended Inventory (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table.  
{#aws-mq-broker__table_ojy_vss_5hc__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
| Configuration item \[configuration_item\] | References the Cloud Messaging Service \[cmdb_ci_cloud_messaging_service\] table. |
[Table 5. Key Value \[cmdb_key_value\]]

{#aws-mq-broker__table_ojy_vss_5hc}

*[\>]: and then