--- 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 Configuration # Amazon MQ Configuration 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 Configuration pattern-based discovery The Amazon MQ Configuration pattern-based discovery enables ServiceNow customers to identify and capture Amazon MQ configurations within their AWS cloud environment using Discovery and Service Mapping Patterns. This functionality requires proper AWS discovery prerequisites and involves activating a specific discovery pattern that is disabled by default. The discovered data is stored across both CMDB and non-CMDB tables, providing a comprehensive view of Amazon MQ configurations. Show full answer Show less ## Key Features * **Activation of the Discovery Pattern:** The Amazon AWS - MQ Configuration - Extended Inventory (LP) pattern must be enabled to perform discovery. Starting with Visibility Content version 6.28.0, activating or deactivating this pattern is seamless and retains update compatibility during upgrades. * **Data Storage:** * **Non-CMDB Tables:** Discovery populates non-CMDB AWS-specific tables, accessible via ServiceNow's Configuration \> AWS navigation. * **CMDB Tables:** Key details about MQ configurations are stored in the CMDB tables, such as *Cloud Resource \[cmdbcicmpresource\]* and *AWS MQ Configuration \[cmdbawsmqconfiguration\]*, including fields like name, ARN, engine type/version, and resource status. * **CI Relationships and References:** The pattern establishes relationships, such as linking the Cloud Resource CI to AWS Datacenter hosts, and references between MQ configuration and cloud resource records to maintain accurate configuration item mapping. * **AWS Tag Discovery:** Tags associated with Amazon MQ configurations are collected and stored in the *Key Value \[cmdbkeyvalue\]* table, enabling tag-based organization and reporting. * **Resource Inclusion List Management:** To avoid duplicate discovery, verify that Amazon MQ resources are not included in the Resource Inclusion List \[sacloudinventoryresourcewhitelist\] table before running discovery. ## Practical Application for ServiceNow Customers By leveraging this pattern-based discovery, customers can automate the identification, tracking, and management of Amazon MQ configurations within their AWS environment. This ensures accurate and up-to-date CMDB data, supports operational and compliance requirements, and enhances cloud resource visibility. Activating the discovery pattern and managing resource inclusion settings are critical first steps to enable effective Amazon MQ configuration discovery. Discovery and Service Mapping Patterns finds Amazon MQ Configurations 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-configuration__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-configuration__activating-disabled-pattern-not-customization} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables. ## Data stored in non-CMDB tables {#aws-mq-configuration__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Amazon AWS - MQ Configuration - 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-configuration__table_non_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the MQ configuration. | | Object ID \[object_id\] | The Amazon Resource Name (ARN) of the MQ configuration. | | Id \[id\] | The unique ID of the MQ configuration. | | Engine Type \[engine_type\] | The type of broker engine the configuration applies to. For example: ACTIVEMQ or RABBITMQ. | | Engine Version \[engine_version\] | The version of the broker engine the configuration applies to. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 1. AWS MQ Configuration \[cmdb_aws_mq_configuration\]] {#aws-mq-configuration__table_non_cmdb} ## Data stored in CMDB tables {#aws-mq-configuration__section_ggp_ql2_bgc} Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - MQ Configuration - Extended Inventory (LP) pattern. {#aws-mq-configuration__table_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the MQ configuration. | | Object ID \[object_id\] | The ARN of the MQ configuration. | | Resource type \[resource_type\] | Type of resource. The value is set to AWS::MQ::Configuration. | | 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 Resource \[cmdb_ci_cmp_resource\]] {#aws-mq-configuration__table_cmdb} ## CI relationships {#aws-mq-configuration__section_dc4_ghc_dgc} The Amazon AWS - MQ Configuration - Extended Inventory (LP) pattern creates the following relationships and references to support Amazon MQ Configuration discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#aws-mq-configuration__table_relationships__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | [Table 3. CI relationships] {#aws-mq-configuration__table_relationships} {#aws-mq-configuration__table_ci_references__entry__3} | CI | Field | Referenced CI | |-|-|-| | AWS MQ Configuration \[cmdb_aws_mq_configuration\] | Configuration Item \[configuration_item\] | Cloud Resource \[cmdb_ci_cmp_resource\] | | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud Resource \[cmdb_ci_cmp_resource\] | [Table 4. CI references] {#aws-mq-configuration__table_ci_references} ## AWS Tag discovery {#aws-mq-configuration__section_lyw_zhc_dgc} The Amazon AWS - MQ Configuration - Extended Inventory (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-mq-configuration__table_ojy_vss_5hc__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | | Configuration item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 5. Key Value \[cmdb_key_value\]] {#aws-mq-configuration__table_ojy_vss_5hc} *[\>]: and then