--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform Release : - australia ft:locale : - de-DE ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Configure using guided setup # Configure API Service Graph Connector for AWS API Gateway using the guided setup {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 Minuten Lesedauer Set up scheduled import jobs to pull in AWS API Gateway data into your CMDB. ## Vorbereitungen Wichtig: Unless there are configuration issues, use SGC Central to configure the connection. The guided setup method for configuration is being deprecated. The authentication mechanism used by the connector is AWS Signature Type (HMAC Authentication Technique) with AWS Security Token Service (STS) token. For information about permissions, see the [API Service Graph Connector for AWS API Gateway - Setup Instructions \[KB1962734\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB1962734) article in the Now Support Knowledge Base. Dependencies and requirements: * The Integration Commons for CMDB store app, which is automatically installed. See [Integration Commons for CMDB](https://servicenow-prod.fluidtopics.net/5PeLd~t3E_8m4pfHwXaYIA "The Integration Commons for CMDB application contains the CMDB Integrations Dashboard and a set of Robust Transform Engine (RTE) transforms and script includes."). * The CMDB CI class models store app, which is automatically installed. See [CMDB CI Class Models app](https://servicenow-prod.fluidtopics.net/VzkxeWzQzhMzcJt3LjhdlA "The CMDB contains base-system classes that store data about configuration items (CIs). The CMDB CI Class Models ServiceNow Store app adds class models that extend the CMDB class hierarchy, including class descriptions, identification rules, identifier entries, and dependent relationships if applicable."). * The ITOM Discovery License plugin (com.snc.itom.discovery.license). You must activate this plugin. * ITOM Licensing plugin (com.snc.itom.license). See [Request Discovery](https://www.servicenow.com/docs/access?context=t_ActivateTheDiscoveryPlugin&version=australia&pubname=australia-it-operations-management&ft:locale=en-US). Role required: admin ## Prozedur 1. Verify that the application scope is set to the API Service Graph Connector for AWS API Gateway application by using the application picker. For more information, see [Application picker](https://www.servicenow.com/docs/access?context=c_ApplicationPicker&version=australia&pubname=australia-application-development&ft:locale=en-US). 2. Navigate to AllService Graph ConnectorsAWS API GatewaySetup. 3. On the Guided Setup page, select Continue. 4. Configure the authentication credentials to send requests to the AWS API Gateway. 1. In the Configure the Connection and Credentials section of the API Service Graph Connector for AWS API Gateway page, select Start. 2. Configure the connection. 1. Select the Configure AWS authentication credentials task. 2. In the Name field, enter a name for the authentication. `SGAwsApiCredentials` is the default credential alias name. You can add multiple AWS API Gateway instances. However, try not to modify the default connection alias. 3. Enter the access key ID and the secret access key in the Access Key ID and Secret Access Key fields respectively. The AWS access keys are long-term credentials for the IAM user and include two parts: an access key ID and a secret access key. You must use both the access key ID and the secret access key together to authenticate requests. 4. Select Update. 5. Set the Configure AWS authentication credentials task to complete by selecting the Mark as complete check box and then select Continue. {#api-sgc-aws-gateway-config__ul_bpr_y2n_21c} 3. Update the required configuration properties for an AWS API Gateway instance and test the connection. 1. Select the Configure and Test AWS Account Details task. 2. In the Service Graph Connections section, review and modify the property details by selecting a property from the Property column in the Service Graph Connection Properties related list. You can configure the following properties: AccountId : A numeric identifier of the AWS account ID. CollectionPeriod(days) : Duration in days for collecting API usage data. CollectUsageData : Enable usage data collection to retrieve API usage data over a specified duration. IsGovCloud : Enable to indicate that the connection setup is for the AWS GovCloud. ConfigAggregatorAccountId : AWS account ID where the aggregator resource type in the AWS Config service has been configured. Region(s) : A list of comma-separated regions where the AWS API Gateway resides. PartitionSize : Partition size for AWS managed APIs if the parallel loading is enabled.Accepts a numeric value greater than zero. If left empty, the value is automatically calculated. StandaloneAccountId : The ID of a member account associated with the AWS API Gateway account. ConfigAggregatorName : The name of the aggregator resource type in the AWS Config service. ManagementAccountId : The management account ID associated with the AWS API Gateway account. ConfigAggregatorRegion : The region where the aggregator resource type resides. StsRoleName : The STS Assume Role name of the AWS account that is used for querying the STS Assume Role API to obtain the API credentials. 3. Select Update in the Service Graph Connection Properties section. 4. Test the connection by selecting the Test Connection related link. Testing the connection might take a few moments. The page is refreshed to show the test results. 5. When the Status field is set to Success, select Update. If any of the tests have errors, follow the suggestions for remediation. 6. Set the Configure and Test AWS Account Details task to complete by selecting the Mark as complete check box and then select Continue. {#api-sgc-aws-gateway-config__ol_ac1_yrt_zzb} {#api-sgc-aws-gateway-config__aws-prop} {#api-sgc-aws-gateway-config__aws-prop} {#api-sgc-aws-gateway-config__substeps_eyb_mff_z1c} 5. **Wahlweise:** Integrate with multiple AWS API Gateway instances. 1. In the Add Multiple Instances section of the API Service Graph Connector for AWS API Gateway page, select Start. 2. Enable creating data sources for the new AWS API Gateway connection. 1. Ensure that you have edit permissions for the Datasource \[sys_data_source\] table. 2. Select the Update Data Source Access task. 3. To edit the record, select the Global application scope from the application picker. 4. In the Application Access related list of the Data Source form that opens in a new tab, select the Can create, Can update, and Can delete check boxes. 5. Select Update. 6. From the application picker, select the API Service Graph Connector for AWS API Gateway application scope. 7. Set the Update Data Source Access task to complete by selecting the Mark as complete check box and then select Continue. {#api-sgc-aws-gateway-config__ol_xwp_3tb_dxb} 3. Enable creating a scheduled import job for the new AWS API Gateway connection. 1. Ensure that you have edit permissions for the Scheduled data import \[scheduled_import_set\] table. 2. Select the Update Data Scheduled Import Access task. 3. To edit the record, select the Global application scope from the application picker. 4. In the Application Access related list of the Scheduled Data Import form, select the Can create, Can update, and Can delete check boxes. 5. Select Update. 6. From the application picker, select the API Service Graph Connector for AWS API Gateway application scope. 7. Set the Update Data Scheduled Import Access task to complete by selecting the Mark as complete check box and then select Continue. {#api-sgc-aws-gateway-config__ol_ulk_jvb_dxb} 4. Clear the cache on the Data Source \[sys_data_source\] and Scheduled Data Imports \[scheduled_import_set\] tables. 1. Select the Clear Cache for Data Source and Scheduled Data Imports tables task. 2. In the Run script text box of the background script page, enter the following script: GlideTableManager.invalidateTable("sys_data_source"); GlideCacheManager.flushTable("sys_data_source"); GlideTableManager.invalidateTable("scheduled_import_set"); GlideCacheManager.flushTable("scheduled_import_set"); GlideTableManager.invalidateTable("sys_db_object"); GlideCacheManager.flushTable("sys_db_object"); 3. Select Run Script to run the background script in the global scope. The script may take several minutes to execute. 4. After the script is executed, select Close. 5. From the application picker, select the API Service Graph Connector for AWS API Gateway application scope. 6. Set the Clear Cache for Data Source and Scheduled Data Imports tables task to complete by selecting Mark as Complete. {#api-sgc-aws-gateway-config__ol_b5x_3wb_dxb} 5. Add another connection for the new AWS API Gateway instance. 1. Verify that the application scope is set to the API Service Graph Connector for AWS API Gateway application by using the application picker. 2. Select the Add Another Connections task and then select Click Here. 3. On the Connections page that opens in another browser tab, select Add Connection. 4. In the Create Connection window, fill in the connection name, access key, and secret key details. 5. Select Create Connection. 6. Close the Workflow Studio and return to the guided setup tab. 7. Set the Add Another Connections task to complete by selecting the Mark as complete check box and then select Continue. {#api-sgc-aws-gateway-config__ol_xg1_tzf_4bc} {#api-sgc-aws-gateway-config__connection-name} {#api-sgc-aws-gateway-config__connection-name} 6. Update the required configuration properties for the new AWS API Gateway connection and test the connection. 1. Select the Test New Connections task. 2. Select the connection record you created in step [5.e](https://servicenow-prod.fluidtopics.net/etmm5WxlNVM0Fc0v8B9Ubg#api-sgc-aws-gateway-config__connection-name). 3. Test the connection by selecting the Test Connection related link. Testing the connection might take a few moments. The page is refreshed to show the test results. 4. When the Status field is set to Success, select Update. If any of the tests have errors, follow the suggestions for remediation. 5. Set the Test New Connections task to complete by selecting the Mark as complete check box and then select Continue. {#api-sgc-aws-gateway-config__ol_jmp_brj_4bc} {#api-sgc-aws-gateway-config__substeps_p3p_vlb_dxb} 6. Configure the scheduled job for the import of AWS API Gateway data. 1. In the Set up Scheduled Import Jobs section of the API Service Graph Connector for AWS API Gateway page, select Start. {#api-sgc-aws-gateway-config__scheduled-import} {#api-sgc-aws-gateway-config__scheduled-import} 2. Select the SGA-AWS-API-Gateway-Managed-API-RESTManaged API Rest scheduled job. For multiple instances, select the scheduled job for the SGA-AWS-API-Gateway-Managed-API-RESTManaged API Rest data source. 3. On the Scheduled Data Import form, verify the field values for the scheduled job. For more information, see [Schedule a data import](https://www.servicenow.com/docs/access?context=t_ScheduleADataImport&version=australia&pubname=australia-integrate-applications&ft:locale=en-US#table_r53_5hm_xp). 4. Select Active check box to activate the scheduled job for the SGA-AWS-API-Gateway-Managed-API-RESTManaged API Rest data source. 5. Select Update. 6. Set the Set up Scheduled Import Jobs task to complete by selecting the Mark as complete check box and then select Continue. 7. On the API Service Graph Connector for AWS API Gateway page, select Complete to save your changes. 8. In Complete setup dialog box, select Complete to complete the setup. 9. In the message box that appears, select Done.