--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Amazon MQ Broker # Amazon MQ Broker pattern-based discovery {#ariaid-title1} * Release version: Yokohama * * 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 detect and map Amazon MQ Brokers within their AWS cloud environments. This discovery uses the Discovery and Service Mapping Patterns application to capture detailed broker information, supporting comprehensive cloud infrastructure visibility and CMDB accuracy. Show full answer Show less ## Key Features * **Pattern Activation:** The Amazon MQ Broker discovery pattern is disabled by default and must be enabled. Updates to patterns after activation are maintained without being treated as customizations. * **AWS Discovery Prerequisites:** Proper AWS discovery prerequisites must be met, including removing resources from the Resource Inclusion List to prevent duplicate discovery. * **GovCloud Support:** Discovery supports AWS GovCloud (US) by requiring appropriate datacenter URLs when configuring AWS service accounts. * **Data Storage:** Discovered data is populated into both CMDB and non-CMDB tables: * **Non-CMDB Data:** Captured by the *Amazon AWS - MQ Broker - Extended Inventory (LP)* pattern and viewable under AWS configuration tables. * **CMDB Data:** Includes Cloud Messaging Service records with installation and operational status. * **CI Relationships and References:** The pattern creates relationships such as "Hosted on" linking Cloud Messaging Services to AWS Datacenters, and references between AWS MQ Broker and Cloud Messaging Service CIs for comprehensive mapping. * **AWS Tag Discovery:** Tags from AWS MQ Brokers are collected and stored in the Key Value table, linked to Cloud Messaging Service configuration items for enhanced metadata management. ## Key Outcomes * Improved visibility into Amazon MQ Brokers in AWS environments, supporting better cloud resource management. * Accurate population of broker attributes such as name, ID, state, engine type/version, and host instance type in ServiceNow CMDB and non-CMDB tables. * Establishment of clear relationships within the CMDB, enabling impact analysis and service mapping related to Amazon MQ Brokers. * Integration of AWS tag information into the CMDB, facilitating enhanced categorization and governance of cloud messaging resources. * Support for AWS GovCloud discovery, enabling compliance and visibility in restricted cloud regions. Discovery and Service Mapping Patterns finds Amazon MQ Brokers on your cloud environment. Discovering some of these resources may 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 [Amazon AWS Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/nnBwzYmMo_kpTZpG3y5~xQ "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources may 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 [Amazon Web Services (AWS) Resource Inventory](https://servicenow-prod.fluidtopics.net/U2bwxjeyIbyEXySOOJQkYA "The ServiceNow Discovery and Service Mapping applications can find and map the AWS resources available by AWS Config Service. Discovering some of these resources may 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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/CvTA68TY3ph_FRR49RbdPg "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