--- 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 DynamoDB Cluster # Amazon DynamoDB Cluster pattern-based discovery {#ariaid-title1} Release version: Australia Updated March 12, 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 DynamoDB Cluster pattern-based discovery The Amazon DynamoDB Cluster pattern-based discovery in ServiceNow enables automated detection and mapping of DynamoDB clusters within your AWS cloud environment. This capability is part of the Discovery and Service Mapping Patterns application, which identifies AWS services and populates configuration management database (CMDB) tables with detailed cluster and node information. It supports continuous updates and integration with AWS GovCloud environments. Show full answer Show less ## Key Features * **Pattern Activation:** The DynamoDB Cluster discovery pattern is disabled by default and requires activation. Starting with Visibility Content version 6.28.0, pattern activation changes are preserved through upgrades without being treated as customizations. * **AWS Prerequisites:** Proper AWS discovery prerequisites must be verified, including ensuring that relevant resources are not listed in the Resource Inclusion List to avoid duplicate discovery. * **Discovery Schedule Configuration:** Supports AWS GovCloud (US) accounts by requiring datacenter URL configuration when setting up AWS service accounts. * **CMDB Data Population:** Runs the Amazon AWS - DynamoDB Cluster - Extended Inventory (LP) pattern to populate detailed DynamoDB cluster and node data into specific CMDB tables. * **AWS Tag Collection:** Captures AWS tags associated with DynamoDB clusters and nodes, storing them in the Key Value CMDB table for enhanced resource metadata management. ## CMDB Data Details * **Cloud DataBase Cluster Table:** Stores cluster-level details such as cluster name, unique cluster ID (ARN), status, type, endpoint (FQDN), node count, and vendor information. * **Cluster Node Table:** Contains node-specific information including node identifier, serial number, node status, endpoint, and references back to the parent cluster. * **Configuration Item Relationships:** Establishes relationships between clusters, nodes, and AWS datacenters to model hosting and membership connections accurately. ## Practical Implications for ServiceNow Customers By enabling this discovery pattern, customers can automate the identification and inventory of DynamoDB clusters and their nodes within the AWS environment, gaining real-time visibility into cluster status, configuration, and relationships. This supports improved asset management, operational insight, and integration with broader IT service management processes. Proper configuration, including prerequisites validation and pattern activation, ensures accurate and up-to-date data in the CMDB, which is critical for effective cloud resource management and compliance. Discovery and Service Mapping Patterns finds AWS services 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-dynamodb-cluster__selection_ipy_53n_jfc} 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-dynamodb-cluster__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."). ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Amazon AWS - DynamoDB Cluster - Extended Inventory (LP) pattern. {#aws-dynamodb-cluster__entry__2} | Field | Description | |-|-| | Name \[name\] | The name assigned to the DynamoDB Accelerator (DAX) cluster. | | Cluster ID \[cluster_id\] | The Amazon Resource Name (ARN) uniquely identifying the DAX cluster. | | Cluster Status \[cluster_status\] | The current operational status of the DAX cluster. | | Cluster Type \[cluster_type\] | Cluster type: DynamoDB Cluster. | | Fully qualified domain name \[fqdn\] | The endpoint address used to connect to the DAX cluster. | | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Node Count \[node_count\] | The total number of nodes in the DAX cluster. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | | Description \[short_description\] | Description of the cluster: DynamoDB Cluster. | | Vendor \[vendor\] | Name of the vendor: Amazon. | [Table 1. Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\]] {#aws-dynamodb-cluster__entry__24} | Field | Description | |-|-| | Name \[name\] | The unique identifier of the DAX node within the cluster. | | Serial Number \[serial_number\] | Unique identifier of the node in the following format: \/node/\. | | Node Status \[node_status\] | The current operational status of the node. For example: available, joining, or deleting. | | Fully qualified domain name \[fqdn\] | The endpoint address used to connect to the specific DAX node. | | Install Status \[install_status\] | Install status of the node. Default value is Installed. | | Operational Status \[operational_status\] | Operational status of the node. Default value is Operational. | | Cluster \[cluster\] | References the Cloud Database Cluster \[cmdb_ci_cloud_db_cluster\] table. | | Description \[short_description\] | Description of the node: DynamoDB Cluster Node. | [Table 2. Cluster Node \[cmdb_ci_cluster_node\]] ## CI relationships The Amazon AWS - DynamoDB Cluster - Extended Inventory (LP) pattern creates these relationships to support Amazon DynamoDB Cluster discovery. {#aws-dynamodb-cluster__entry__43} | CI | Relationship | CI | |-|-|-| | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | Cluster Node \[cmdb_ci_cluster_node\] | Hosted on::Hosts | AWS Datacenter \[cmdb_ci_aws_datacenter\] | | Cluster Node \[cmdb_ci_cluster_node\] | Cluster of::Cluster | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] | | Cluster Node \[cmdb_ci_cluster_node\] | References | Cloud DataBase Cluster \[cmdb_ci_cloud_db_cluster\] | [ ] ## AWS tag discovery {#aws-dynamodb-cluster__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#aws-dynamodb-cluster__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#aws-dynamodb-cluster__table_axq_spc_y2c}