--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # AWS resources used by the connector # AWS resources used by the Service Graph Connector for AWS {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 AWS Resources Used by the Service Graph Connector for AWS The Service Graph Connector for AWS integrates with various AWS services to facilitate resource management and configuration tracking. Key services include AWS Config, AWS Systems Manager, and AWS Systems Manager Inventory, each serving specific functions essential for the connector's operation. Show full answer Show less ## Key Features * **AWS Config Service and Configuration Recorder:** These are mandatory for setting up the connector, monitoring AWS resource configurations, and capturing changes as configuration items (CIs). The connector includes a script (EnableAWSConfig.yml) to enable this service. * **AWS Config Aggregator:** This optional feature aggregates configuration data from multiple accounts and regions, improving data retrieval efficiency. It eliminates the need to access each account or region individually, facilitating quicker updates. * **AWS Systems Manager:** This service is required for the deep discovery feature, which gathers detailed server data from EC2 instances. It necessitates the installation of the SSM Agent and the appropriate IAM role on instances. * **AWS Systems Manager Inventory:** It is used to collect software data from EC2 instances and requires configuration in each AWS region for effective operation. ## Key Outcomes By leveraging these AWS resources, customers can expect enhanced visibility and control over their AWS infrastructure. The integration enables efficient configuration tracking, deep discovery of server data, and comprehensive software inventory management across multiple AWS accounts and regions. This leads to improved operational efficiency and better compliance posture. Get familiar with the AWS concepts to learn how the Service Graph Connector for AWS is integrated with Amazon Web Services (AWS). ## AWS Config service and configuration recorder {#sgc-cmdb-aws-concepts__section_gbm_2g4_fzb} Important: The AWS Config service and AWS configuration recorder are required for setting up the connector. The AWS Config service monitors and records changes to your AWS resource configurations. The AWS configuration recorder detects changes in resource configurations and captures these changes as configuration items (CIs). The is required for setting up the connector. The configuration recorder enables recording all hardware data in AWS Config. See [What Is AWS Config?](https://docs.aws.amazon.com/config/latest/developerguide/WhatIsConfig.html) on the AWS Documentation site. The Service Graph Connector for AWS includes the EnableAWSConfig.yml script to enable the AWS Config service that instead enables the configuration recorder. See [Executing scripts required for setting up AWS](https://www.servicenow.com/docs/3RY69g208Sr5UUaV0K~Qcg "You must execute scripts provided with the Service Graph Connector for AWS to set up the AWS environment for importing data."). Note: Ensure that the AWS Config service is enabled for all applicable AWS accounts and regions. ## AWS Config aggregator {#sgc-cmdb-aws-concepts__section_ywn_kg4_fzb} Important: The AWS Config aggregator is optional for setting up the connector. The AWS Config aggregator collects the AWS Config configuration and compliance data from the following sources: * Multiple accounts and multiple regions * Single account and multiple regions * An organization in AWS organizations and all the accounts within the organization that have AWS Config enabled. {#sgc-cmdb-aws-concepts__ul_i5r_s42_jzb} The advantages of using an AWS Config aggregator with the Service Graph Connector for AWS are: * Gets all the data from a single location. * Gets the bootstrap updates (baseline configurations) and the incremental updates (new configurations added after the last update). * Doesn't require looping into each account and region. * Accelerates pulling data. {#sgc-cmdb-aws-concepts__ul_kvz_2dg_jzb} Due to these advantages, consider leveraging the AWS Config aggregator for pulling data from multiple accounts or multiple regions. Note: For detecting any deleted resources, the connector uses the config:ListDiscoveredResources API to loop through each AWS account and region and update the CMDB CI accordingly. As a date range for selecting resources can't be specified in the ListDiscoveredResources API, the connector might make multiple API calls to gather all the data that might impact the performance of the connector. For more information on setting up an AWS Config aggregator, see [Multi-Account Multi-Region Data Aggregation](https://docs.aws.amazon.com/config/latest/developerguide/aggregate-data.html) and [Setting Up an Aggregator Using the Console](https://docs.aws.amazon.com/config/latest/developerguide/setup-aggregator-console.html) on the AWS Documentation site. ## AWS Systems Manager and AWS Systems Manager Inventory {#sgc-cmdb-aws-concepts__section_zcw_f34_fzb} Important: AWS Systems Managerand AWS Systems Manager Inventory are required for setting up the deep discovery feature. The AWS Systems Manager enables fetching server data, also called as deep discovery data, from EC2 instances across AWS accounts and regions through SSM documents. The deep discovery data includes host name, serial number, CPU data, TCP data, and process information. The AWS Systems Manager Inventory imports the software data installed on the EC2 instances. The Inventory resource group in AWS Systems Manager collects information about the EC2 instances and the software applications installed on them. Ensure that the following items are configured in all AWS accounts: * The AWS Systems Manager Agent (SSM Agent) is installed on all managed EC2 instances. * The AmazonSSMForInstancesRole IAM instance profile role is attached as the instance profile on EC2 instances. * The AWS Systems Manager Inventory is configured in each AWS region. * The AWS Systems Manager has access to the managed EC2 instances. Note: By default, AWS Systems Manager doesn't have permission to perform actions on EC2 instances. You can grant access by attaching the AmazonSSMForInstancesRole IAM instance profile role to the EC2 instance. See [Setting up AWS Systems Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-prereqs.html) on the AWS Documentation site. {#sgc-cmdb-aws-concepts__ul_ix2_334_fzb} The advantages of using AWS Systems Manager and AWS Systems Manager Inventory are: * The AWS Systems Manager enables getting the detailed server data such as host name, serial number, CPU data, TCP data, and process information. * The AWS Systems Manager Inventory enables the server classification and getting the software data. {#sgc-cmdb-aws-concepts__ul_unq_twg_tzb}