{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":29889,"path":"it-operations-management/discovery-and-service-mapping-patterns/aws-dynamoDB-discovery.md","title":"Amazon DynamoDB discovery using Patterns","bundle":null,"doc_type":null,"release":"australia","body":"\n# Amazon DynamoDB discovery using Patterns\n\nThe ServiceNow Discovery and Service Mapping applications use the Amazon AWS DynamoDB pattern to find components of DynamoDB. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.\n\nThe Amazon AWS DynamoDB pattern deploys REST APIs for fetching information about DynamoDB. You can also configure Service Mapping and Discovery to discover AWS DynamoDB components using AWS events.\n\nThe ServiceNow AI Platform supports Amazon Commercial Cloud Services \\(C2S\\) for discovery and cloud governance. C2S is the government program that brings AWS into the Intelligence Community.\n\n## Request apps on the Store\n\nVisit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\n## Prerequisites\n\n-   **User access**\n\n    On the AWS Console, provide a user with the following permissions: AmazonDynamoDBReadOnly Access and AWSLambdaInvocation-DynamoDB.\n\n-   **Cloud Service Account**\n\n    On the ServiceNow AI Platform®, set up the service account with these properties:\n\n    -   An **Account ID**, which is the Amazon account ID to which DynamoDB belongs. Use the Account ID as it appears in the AWS Management Console.\n    -   The appropriate AWS credentials required for the account ID to reach the AWS cloud.\n-   **AWS Credentials**\n\n    On the ServiceNow AI Platform®, configure AWS credentials, using a secret key and an access key.\n\n-   **Entry point for service containing DynamoDB**\n\n    Use **AWS Resource Name Endpoint** as the Entry Point Type when creating a service containing DynamoDB. Provide the Amazon Resource Name \\(ARN\\) and host for the entry point.\n\n-   **\\(For top-down discovery by Service Mapping\\) Run horizontal discovery of the Logical Datacenters**\n\n    Discover Logical Datacenters hosting DynamoDBs as described in Run Discovery on an AWS cloud service account in the ServiceNow Cloud Provisioning and Governance documentation.\n\n-   **Cloud Discovery**\n\n    For Cloud Discovery, download the Discovery and Service Mapping pattern from the ServiceNow Store.\n\n-   **MID Server**\n\n    When installing the MID Server, ensure that the host machine meets or exceeds the [MID Server system requirements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerSystemRequirements.md).\n\n-   **Discovery schedule**\n\n    Create a schedule for the relevant AWS service account as described in Schedule Discovery on a service account in the ServiceNow Cloud Provisioning and Governance documentation.\n\n-   **Configure AWS event service**\n\n    To enable alert-based discovery, configure the AWS event service as described in Set up AWS event processing for Discovery and Service Mapping in the ServiceNow Cloud Provisioning and Governance documentation.\n\n\n## Verify the REST API permissions\n\nDownload the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.\n\n**Note:** You can test the AWS REST APIs using Postman API platform. For more information, see the [How to test AWS REST API using POSTMAN \\[KB0782183\\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0782183) article in the Now Support Knowledge Base.\n\n## Data collected by Discovery during horizontal discovery\n\n<table id=\"table_td3_psz_42b\"><thead><tr><th>\n\nTable and field\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td colspan=\"2\">\n\nDynamoDB Global Table \\[cmdb\\_ci\\_dynamodb\\_global\\_table\\]\n\n</td></tr><tr><td>\n\nObject ID \\[object\\_id\\]\n\n</td><td>\n\nThe Amazon Resource Name \\(ARN\\), expressed in this format: **arn:aws:dynamodb::xxxxxxxxxxxx:table:&lt;table name&gt;**\n\n</td></tr><tr><td colspan=\"2\">\n\nDynamoDB Table \\[cmdb\\_ci\\_dynamodb\\_table\\]\n\n</td></tr><tr><td>\n\nName \\[name\\]\n\n</td><td>\n\nTable name.\n\n</td></tr><tr><td>\n\nCreation date \\[creation date\\]\n\n</td><td>\n\nCreation date of DynamoDB according to the time zone of the MID Server that discovers this DynamoDB.\n\n</td></tr><tr><td>\n\nCloud provider \\[cloud\\_provider\\]\n\n</td><td>\n\nAmazon AWS\n\n</td></tr><tr><td>\n\nObject ID \\[object\\_id\\]\n\n</td><td>\n\nThe Amazon Resource Name \\(ARN\\), expressed in this format: **arn:aws:dynamodb:&lt;region&gt;:xxxxxxxxxxxx:table:&lt;table name&gt;**\n\n</td></tr><tr><td>\n\nGlobal ARN \\[global\\_arn\\]\n\n</td><td>\n\nThe global ARN of the table for the global DynamoDB table. This field is empty if the DynamoDB is not global.\n\n</td></tr><tr><td>\n\nStream ARN \\[stream\\_arn\\]\n\n</td><td>\n\nThe choices are:-   Stream ARN\n-   Disabled\n\n</td></tr><tr><td>\n\nService name \\[service\\_name\\]\n\n</td><td>\n\nSet to **DynamoDB** by default.\n\n</td></tr><tr><td>\n\nEncryption \\[encryption\\]\n\n</td><td>\n\nEncryption configuration on DynamoDB. The choices are:-   Enabled\n-   Disabled\n\n</td></tr><tr><td>\n\nReplication group \\[replication\\_group\\]\n\n</td><td>\n\nTable ARN of the connected global DynamoDB tables.\n\n</td></tr><tr><td>\n\nRead Autoscaling \\[read\\_autoscaling\\]\n\n</td><td>\n\nThe choices are:-   Enabled\n-   Disabled\n\n</td></tr><tr><td>\n\nRead Units \\[read\\_units\\]\n\n</td><td>\n\nThe number of read units on the DynamoDB table.\n\n</td></tr><tr><td>\n\nRead Max Units \\[read\\_max\\_units\\]\n\n</td><td>\n\nThe maximum allowed number of read units on the DynamoDB table.\n\n</td></tr><tr id=\"store-12-2018\"><td>\n\nRead Min Units \\[read\\_min\\_units\\]\n\n</td><td>\n\nThe minimum allowed number of read units on the DynamoDB table.\n\n</td></tr><tr><td>\n\nWrite Units \\[write\\_units\\]\n\n</td><td>\n\nThe number of write units on the DynamoDB table.\n\n</td></tr><tr><td>\n\nWrite Max Units \\[write\\_max\\_units\\]\n\n</td><td>\n\nThe maximum allowed number of write units on the DynamoDB table.\n\n</td></tr><tr><td>\n\nWrite Min Units \\[write\\_min\\_units\\]\n\n</td><td>\n\nThe minimum allowed number of write units on the DynamoDB table.\n\n</td></tr><tr><td>\n\nTable Size \\[table\\_size\\]\n\n</td><td>\n\nThe currently provisioned size of the DynamoDB table in bytes.\n\n</td></tr><tr><td>\n\nWrite Autoscaling \\[write\\_autoscaling\\]\n\n</td><td>\n\nThe choices are:-   Enabled\n-   Disabled\n\n</td></tr><tr><td>\n\nPoint-in-Time \\[point\\_in\\_time\\]\n\n</td><td>\n\nThe choices are:-   Enabled\n-   Disabled\n\n</td></tr></tbody>\n</table>The graphic illustrates CIs that are part of DynamoDB discovery.\n\n\\[Omitted image \"DynamoDB-components.png\"\\] Alt text: DynamoDB components\n\n## CI relationships\n\nThe Amazon AWS DynamoDB pattern creates the following CI relationships:\n\n|CI|Relationship|CI|\n|---|------------|---|\n|DynamoDB Global Table \\[cmdb\\_ci\\_dynamodb\\_global\\_table\\]|Cluster of::Cluster|DynamoDB Table \\[cmdb\\_ci\\_dynamodb\\_table\\]|\n\n## Data collected by Service Mapping during top-down discovery\n\nThe Amazon AWS DynamoDB pattern identifies connections from the DynamoDB to AWS Lambda functions.\n\n## Troubleshooting\n\nIf the mapping process does not proceed as you expected, follow the following suggestions.\n\n<table id=\"table_ggn_ypj_yhb\"><thead><tr><th>\n\nSymptom\n\n</th><th>\n\nCause\n\n</th><th>\n\nSolution\n\n</th></tr></thead><tbody><tr><td>\n\nDiscovery fails. The discovery message contains the information about an error caused by the REST timeout.\n\n</td><td>\n\nThere are many CIs sending the REST call response in the deployment. The MID Server cannot process the REST call response without exceeding the time limit controlled by the **mid.sa.cloud.request\\_timeout** parameter.\n\n</td><td>\n\nBy default, the **mid.sa.cloud.request\\_timeout** parameter is set to 30000 milliseconds. Increase the value of this parameter on the relevant MID Server and run discovery again.\n\n**Note:** If the **Configuration Parameters** related list for the relevant MID Server does not show this parameter, you may need to add it.\n\n</td></tr><tr><td>\n\nPattern Designer fails during a debug session. The Pattern Designer message contains information about an error caused by a timeout.\n\n</td><td>\n\nThe Pattern Designer fails because of a timeout during pattern debugging \\(and not during discovery\\).\n\n</td><td>\n\nBy default, the **sa.debugger.max\\_timeout**parameter is set to 240 seconds.Increase the value of this parameter on the relevant MID Server.\n\n</td></tr></tbody>\n</table>**Parent Topic:**[AWS discovery using patterns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/data-discovered-aws-patterns.md)\n\n**Related topics**  \n\n\n[Define a Cloud REST Query for cloud computing devices](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/cloud-rest-query-pattern.md)\n\n"}}