Amazon Redshift discovery

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 1 minute to read
  • The ServiceNow® Discovery application uses the Amazon AWS Redshift pattern to find Redshift data warehouse services available on Amazon Web Services (AWS).

    Redshift runs as a cluster of compute nodes with an additional leader node. The leader node acts as an interface with client applications and coordinates communication between the compute nodes.

    Visit the ServiceNow Store website 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.

    Prerequisites

    Verify the following application is installed
    Discovery and Service Mapping Patterns
    Configure AWS service account
    Configure AWS service account on the ServiceNow AI Platform. For more information, see Set up AWS service accounts.

    Verify the REST API Permissions

    Download the Cloud Discovery patterns spreadsheet 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.

    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] article in the Now Support Knowledge Base.

    Data collected by Discovery during horizontal discovery

    Discovery populates the data in the CMDB when running the Amazon AWS Redshift pattern.

    Table 1. Cloud Database [cmdb_ci_cloud_database]
    Field Description
    Start date Time at which the Redshift cluster was created.
    Name Name of the Redshift cluster.
    VPC ID Identifier of the virtual private cloud that includes the cluster.
    Cluster availability status Status of the cluster, such as:
    • Available
    • Unavailable
    • Maintenance
    • Modifying
    • Failed
    Node count Number of nodes in the cluster.
    Availability zone AWS availability zone where the cluster is deployed.
    Node type Type of nodes in the cluster, such as:
    • dc2
    • ds2
    • ra3
    FQDN Fully qualified domain name of the cluster.
    TCP port Port that the cluster uses for listening.