Service Graph Connector for AWS
Summarize
Summary of Service Graph Connector for AWS
The Service Graph Connector for AWS allows you to securely integrate Amazon Web Services (AWS) data into your ServiceNow instance, enhancing visibility and control over cloud resources. This integration leverages AWS native technologies and best security practices, making it ideal for cloud teams managing workflows in ServiceNow.
Show less
Key Features
- Visibility: Gain insights into cloud resources, relationships, and states.
- Deep Discovery: Supports IT Asset Management (ITAM) and Software Asset Management (SAM) outcomes.
- Governance and Compliance: Aids in meeting regulatory requirements.
- Connection Configuration: Use SGC Central for managing connections, ensuring efficient lifecycle management.
- BYOL Support: Facilitates bringing your own licenses for Oracle Database servers on AWS.
- Event-Based Discovery: Automatically updates CIs based on AWS events.
- Shared VPC and Subnets: Import relationships among resources across different AWS accounts.
Key Outcomes
By utilizing the Service Graph Connector for AWS, customers can expect streamlined integration of AWS data, improved management of cloud resources, and enhanced visibility into their IT environment. Steps include ensuring proper configurations, performing full data imports post-upgrade, and utilizing monitoring dashboards for a comprehensive view of integration status.
Use the Service Graph Connector for AWS to securely bring in Amazon Web Services (AWS) data into your ServiceNow instance.
Request apps on the Store
Visit the ServiceNow Store 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.
The integration uses AWS native technologies and AWS security best practices to enable cloud teams to connect the data within their ServiceNow workflow. For more information about the Service Graph Connector for AWS, see the Service Graph Connector for AWS - Introduction article on the ServiceNow Community site.
Supported ServiceNow versions
- Yokohama
- Zurich
- Australia
Use cases
The following are examples on how you can use the Service Graph Connector for different ServiceNow applications:
- Visibility into cloud resources, relationships, and state.
- Deep discovery of applications for ITAM or SAM outcomes.
- Governance and compliance outcome.
Important information for upgrading Service Graph Connector for AWS
- If there are any customizations, delete the records associated with the Service Graph Connector for AWS from the Customer Updates [sys_update_xml] table. See Customer Updates table.
- Upgrade any dependencies.
- Perform a full import of data from your AWS instance. Verify that the Use last run datetime field value is cleared for all the AWS data sources in the Data Source [sys_data_source] table.
- Download and rerun the AWS scripts. See Configure the AWS environment.
Configuring a connection for the connector
CMDB integrations dashboard
The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed integrations. You can see metrics for all integration runs. You can filter the view to a specific CMDB integration, a specific time duration, or a specific integration run. For more details about monitoring AWS integrations in the CMDB Integrations Dashboard, see Using the CMDB Integrations Dashboard.
BYOL support
Bringing your own licenses (BYOL) is the process of bringing previously purchased on-premises licenses to Amazon AWS Cloud. The connector supports the BYOL of the Image CIs for Oracle Database servers on Amazon AWS Cloud by populating the Key Value [cmdb_key_value] table with the licensing information. When the licensing information is found, the key is set to Windows_OS_License_Type_automatic
and the key value is set to BYOL in the Key Value [cmdb_key_value] table.
To support BYOL, the sn_aws_integ.load_all_images system property is enabled during the initial pull to import the metadata of all Image CIs included in the SG-AWS-Image-Id data source. After the initial pull, the property is deactivated automatically. The SG-AWS-Image-Id data source then imports the metadata of the Image CIs without names only.
Event-based discovery
The Service Graph Connector for AWS works with event-based discovery. Events that are pulled from AWS can create and update CIs that were brought by the Service Graph Connector for AWS.
Managing retired CIs in EKS components
If the Amazon Elastic Kubernetes Services (EKS) CIs are deleted in EKS components such as pods, services, and volumes, the corresponding CI entries are automatically set to Retired in the following CMDB CI classes:
Kubernetes Cluster, Kubernetes Node, Kubernetes Pod, Kubernetes Service, Kubernetes DaemonSet Kubernetes Namespace, Kubernetes Deployment, Docker Container, Kubernetes Volume
Shared VPC and subnets support
Import CI relationships established between virtual private clouds (VPCs), subnets, and network interfaces hosted in different AWS accounts. For example, a VPC in one AWS account can be connected to a subnet in the same account, which can then link to a network interface and a virtual machine in another AWS account.
Additional resources
See the following articles on the ServiceNow Community site for any additional information on the AWS set up:
Related content
Data mapping for Service Graph Connector for AWS
CMDB classes targeted in Service Graph Connector for AWS
Enable optimized deletion of retired CIs in AWS
Enable optimized SG-AWS-SendCommand data source performance
Handling import failures for large AWS resources
Handling memory utilization errors for Service Graph Connector for AWS
Life cycle management of records in Service Graph Connector for AWS