{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22769,"path":"intelligent-experiences/ai-control-tower/aws_0.md","title":"AI Service Graph Connector for Amazon","bundle":null,"doc_type":null,"release":"australia","body":"\n# AI Service Graph Connector for Amazon\n\nThe AI Service Graph Connector for Amazon enables you to discover and import AI assets from your AWS environment into ServiceNow AI Control Tower.\n\nThe connector integrates with your AWS account \\(Amazon Bedrock, Amazon SageMaker, Amazon CloudWatch, and Amazon Bedrock AgentCore\\) to catalog AI systems, agents, models, prompts, and tools. Usage data is automatically collected and populated into the AI Control Tower value dashboard, providing comprehensive visibility and governance of your AI operations.\n\n## Download apps from the Store\n\nVisit the ServiceNow store website to download the [AI Service Graph Connector for Amazon](https://store.servicenow.com/store/app/74d7378e47a73a50cbbce551336d4356) application.\n\n## Supported ServiceNow versions\n\nThis connector is supported on the following ServiceNow releases:\n\n|Release|Status|\n|-------|------|\n|Australia|Supported|\n|Zurich|Supported|\n|Yokohama|Supported|\n\n## User Roles\n\nYou must have one of the following roles assigned.\n\n|Required Roles|\n|--------------|\n|sn\\_ai\\_disc.discovery\\_admin|\n|sn\\_cmdb\\_int\\_util.sgc\\_admin|\n\n## ServiceNow Prerequisites\n\nComplete the following setup steps once when configuring the connector for the first time.\n\n**Note:** Updating data source access and clear cache is a prerequisite that needs to be completed only once, when setting up a new instance for the first time.\n\n**Update Data Source Access**\n\nThe connector requires write permissions to the Data Source table to create data sources.\n\nTo enable data source creation:\n\n1.  Select **Global** from the application picker.\n2.  Navigate to **Application Access**.\n3.  Select the **Can create**, **Can update**, and **Can delete** check boxes.\n4.  Select **Update**.\n5.  Switch to the connector application scope.\n\nClear the cached data for the Data Source and Tables.\n\nTo clear the cache:\n\n1.  Navigate to **System Definition** &gt; **Background Scripts**.\n2.  Enter the following script in the **Run Script** text box:\n\n    ```\n    GlideTableManager.invalidateTable('sys_data_source');\n    GlideCacheManager.flushTable('sys_data_source');\n    GlideTableManager.invalidateTable('sys_db_object');\n    GlideCacheManager.flushTable('sys_db_object');\n    \n    ```\n\n3.  Select **Run Script**.\n\n    **Note:** The script might take several minutes to complete. After completion, switch to the connector application scope.\n\n\n## AWS Prerequisites\n\n**AWS prerequisites for version 1.1.0**\n\nComplete the following steps in your Azure environment before creating an Azure Foundry connection. Configure OAuth Credentials:\n\nThe connector uses OAuth to authenticate with Azure APIs. To obtain credentials, register an application in Microsoft Entra ID. For full instructions, see, [https://learn.microsoft.com/en-us/rest/api/azure/\\#register-your-client-application-with-azure-ad](https://learn.microsoft.com/en-us/rest/api/azure/#register-your-client-application-with-azure-ad)\n\nThe Azure client application requires the following roles:\n\n-   Reader role at the subscription or resource group level to discover resources.\n-   Foundry User role in the Azure AI Foundry resources.\n\n**Note:** Starting from March 2026, ServiceNow supports the new Azure AI Foundry alongside the original Foundry. The New Foundry treats each agent version as a distinct entity.\n\n**AWS prerequisites for version 2.0.2**\n\nThe AWS connector requires a read-only IAM user and a read-only role deployed across the accounts you want to discover. Download the CloudFormation templates from the playbook and deploy them using the AWS CloudFormation console as a Stack \\(single account\\) or a StackSet \\(multiple accounts across the Organization\\).\n\nBefore proceeding, confirm you have:\n\nAWS Account- Active AWS account with access to the services you want to connect to.\n\nRequired IAM permissions\n\nThe IAM roles created by the templates earlier grant read-only access to the following services:\n\n-   Amazon Bedrock\n-   Amazon SageMaker\n-   Amazon CloudWatch Logs\n-   Amazon Bedrock AgentCore\n-   AWS Organizations\n-   Amazon EC2\n\nPre-Deployment Checklist\n\nBefore deploying any templates, confirm the following:\n\nYou have AWS CloudFormation Stack and StackSet deployment permissions in the relevant accounts.\n\nTarget member accounts have Amazon Bedrock, SageMaker, and/or AgentCore enabled - accounts without these services will return 403 errors during discovery.\n\nIf using Standalone Mode, confirm the target account ID where SgAictReadOnlyAccessRole.yml will be deployed.\n\nIf using StackSet deployment, confirm that Automatic Deployment is enabled so newly created accounts are covered automatically.\n\nThe default role name across all templates is SgAictReadOnlyAccessRole. If your organization requires a different naming convention, update it consistently across all templates and in the ServiceNow connector configuration before deployment.\n\nPerform the AWS prerequisites:\n\n**1. Choose your deployment scenario**\n\nDetermine how your ServiceNow IAM user will be setup in AWS:\n\n1.  Scenario 1- Management Account: The ServiceNow IAM user is created directly in the AWS Org/Management account.\n2.  Scenario 2- Delegated Member Account: The ServiceNow IAM user is created in a dedicated member account, with a cross-account role in the Management account for Organizational-level access.\n3.  Standalone Mode: Available in both scenarios. Use this to test discovery against a single AWS account before rolling out to the full organization.\n\nTemplates required per scenario\n\n<table id=\"table_xcn_hfy_yjc\"><tbody><tr><td>\n\nTemplate\n\n</td><td>\n\nDeployed as\n\n</td><td>\n\nScenario 1\n\n</td><td>\n\nScenario 2\n\n</td></tr><tr><td>\n\nServiceNowAictUser.yml\n\n</td><td>\n\nStack\n\n</td><td>\n\n✔ \\(Management account\\)\n\n</td><td>\n\n✔ \\(Designated Member account\\)\n\n</td></tr><tr><td>\n\nSgcAictReadOnlyAccessRole.yml\n\n</td><td>\n\nStackSet\n\n</td><td>\n\n✔ \\(all member accounts\\)\n\n</td><td>\n\n✔ \\(all member accounts\\)\n\n</td></tr><tr><td>\n\nSgcAictReadOnlyOrgAccessRole.yml\n\n</td><td>\n\nStack\n\n</td><td>\n\n—\n\n</td><td>\n\n✔ \\(Management account\\)\n\n</td></tr></tbody>\n</table>**2. Download the CloudFormation templates**\n\nDeploy the following AWS CloudFormation templates based on your selected scenario:\n\n1.  Navigate to the connector playbook, open the **Prerequisites** section.\n2.  Select **Download basic scripts**. This downloads a ZIP file containing the following CloudFormation templates:\n    1.  ServiceNowAictUser.yml- Required in all scenarios. Deploy in the account where the ServiceNow IAM user will reside:\n        -   Management account for Scenario 1\n        -   Designated account for Scenario 2\n    2.  SgcAictReadOnlyAccessRole.yml- Required in all scenarios. Deploy across all member accounts via StackSet for Organization-wide discovery, or in a single target account for Standalone Mode.\n    3.  SgcAictReadOnlyOrgAccessRole.yml- Required only for Scenario 2. Deploy in the Org/Management account to grant the Designated account cross-account Organization read access.\n3.  Sign in to [https://console.aws.amazon.com](https://console.aws.amazon.com) using your Management account.\n4.  Extract the ZIP so the template files are available on your local machine.\n\n**3. Enable trusted access for StackSets**\n\nService-managed StackSets require trusted access between AWS Organizations and CloudFormation. This is a one-time setup in the Management account.\n\n1.  Sign in to the Management account.\n2.  Search for CloudFormation in the left navigation pane and select **StackSets**.\n3.  If trusted access is not enabled, a banner prompts you to enable it. Select **Enable trusted access**.\n\n    **CLI Alternative:**\n\n    ```\n    aws organizations enable-aws-service-access\\\n    --service-principal member.org.stacksets.cloudformation.amazonaws.com\n    ```\n\n\n**Note:** For more information, see the AWS documentation on [enabling trusted access with AWS Organizations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-activate-trusted-access.html).\n\n**4. Deploy the ServiceNow IAM user \\(Stack\\)**\n\nThe ServiceNowAictUser.yml template creates the ServiceNow IAM user with the required read-only permissions. Deploy it as a Stack in the account where the user should reside — the Management account for Scenario 1, or the Designated Member account for Scenario 2.\n\n1.  Sign in to the account where the user will be created.\n2.  Search for CloudFormation and select **Create stack** With new resources \\(standard\\).\n3.  Under Specify template:\n    1.  Prepare template: Choose an existing template.\n    2.  Template source: Upload a template file.\n    3.  Select **Choose file** and upload ServiceNowAictUser.yml and select **Next**.\n4.  Under **Specify stack details**:\n    1.  Stack name: aict-servicenow-user.\n    2.  Parameters:\n        -   UserAccountType: ManagementAccount \\(Scenario 1\\) or DesignatedMemberAccount \\(Scenario 2\\)\n        -   SNUserName: servicenow-aict-user\n        -   MbrActRoleName: Leave the default value \\(SgcAictReadOnlyAccessRole\\).\n    3.  Select **Next**.\n5.  Under **Configure stack options**, leave the default values and select **Next**.\n6.  On the **Review and create** page, scroll to the bottom and select **I acknowledge that AWS CloudFormation might create IAM resources** check box.\n7.  Select **Submit**. The stack status shows CREATE\\_IN\\_PROGRESS, then CREATE\\_COMPLETE.\n8.  Open the stack, select the **Outputs** tab, and note the **ServiceNowUserARN** value.\n\n**Note:** The IAM resources created are strictly read-only and scoped to AI Discovery APIs \\(Bedrock, SageMaker, AgentCore, and CloudWatch Logs\\).\n\n**5. Deploy the Org-access role \\(Scenario 2 only, Stack\\)**\n\n**Note:** This step applies only to Scenario 2 \\(user in a Designated Member account\\). Skip it for Scenario 1.\n\nThe SgcAictReadOnlyOrgAccessRole.yml template creates a read-only role in the Management account, scoped to Organization, Account, and Region APIs. The ServiceNow user assumes this role to enumerate the Organization.\n\n1.  Sign in to the **Management account**.\n2.  Search for CloudFormation, then select **Create stack** with new resources \\(standard\\).\n3.  Under **Specify template**:\n    1.  Prepare template: Choose an existing template.\n    2.  Template source: Upload a template file.\n    3.  Select **Choose file** and upload SgcAictReadOnlyOrgAccessRole.yml.\n    4.  Select **Next**.\n4.  Under **Specify stack details**:\n    1.  Stack name: aict-org-readonly-role\n    2.  Parameters:\n        -   DesignatedAccountId: the 12-digit account ID where the ServiceNow user was created \\(Prerequisite 4\\).\n        -   ServiceNowUserName: servicenow-aict-user\n    3.  Select **Next**.\n5.  Under **Configure stack options**, leave the default values and select **Next**.\n6.  On the **Review and create** page, scroll to the bottom and select the check box **I acknowledge that AWS CloudFormation might create IAM resources**.\n7.  Select **Submit** and wait for CREATE\\_COMPLETE.\n\n**Note:** This template is not needed for Scenario 1, because the user created in the Management account already has Organization permissions inline.\n\n**6. Deploy the member-account role \\(StackSet\\)**\n\nThe SgcAictReadOnlyAccessRole.yml template creates the SgcAictReadOnlyAccessRole read-only role that the ServiceNow user assumes to make API calls in each member account. Deploy it as a StackSet from the Management account across all member accounts.\n\n1.  Sign in to the **Management account**.\n2.  Search for CloudFormation in the left navigation pane, select **StackSets** &gt; **Create StackSet**.\n3.  Under **Permissions**, select **Service-managed permissions**.\n4.  Under **Specify template**:\n    1.  Prepare template: Choose an existing template.\n    2.  Template source: Upload a template file.\n    3.  Select **Choose file** and upload SgcAictReadOnlyAccessRole.yml.\n    4.  Select **Next**.\n5.  Under **Specify StackSet** details:\n    1.  StackSet name: aict-member-readonly-role\n    2.  Parameters:\n        -   ServiceNowUserAccountId: the 12-digit account ID where the ServiceNow user was created \\(Management account for Scenario 1, Designated Member account for Scenario 2\\).\n        -   ServiceNowUserName: servicenow-aict-user\n        -   RoleName: leave default \\(SgcAictReadOnlyAccessRole\\)\n    3.  Select **Next**.\n6.  Under **Configure StackSet** options, leave the default values and select **Next**.\n7.  Under **Set deployment** options:\n    1.  Add stacks to stack set: Deploy new stacks\n    2.  Deployment targets — select one of the following:\n        -   Deploy to organization — Deploys to all accounts in the Organization\n        -   Deploy to organizational units \\(OUs\\) — Select **Add an OU** and paste the target OU ID\\(s\\).\n        -   For a subset of accounts within an OU, set **Account filter type** to **Intersection** and provide the specific account numbers.\n    3.  Automatic deployment: Enabled — accounts added to the Organization or OU in the future automatically receive the role.\n    4.  Account removal behavior: Delete stacks.\n    5.  Specify regions: Add the region\\(s\\) matching your connector configuration \\(for example, us-east-1\\).\n    6.  Select **Next**.\n8.  On the **Review page**, select the **I acknowledge that AWS CloudFormation might create IAM resources** check box, then select **Submit**.\n9.  On the **Operations** tab, monitor the StackSet operation until the status shows SUCCEEDED.\n\n**Note:**\n\nIAM is a global service. Although a region must be specified for the StackSet, the role created by this template is global and identical regardless of region. For more information, see the AWS documentation on [creating StackSets with service-managed permissions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-associate-stackset-with-org.html).\n\nStandalone Mode: To validate against a single account before deploying org-wide, deploy SgcAictReadOnlyAccessRole.yml as a regular Stack \\(following the Prerequisite 4\\) in that one account. After validation, deploy the StackSet across all accounts.\n\n**7. Generate the access key**\n\nThe connector requires an Access Key ID and Secret Access Key from the IAM user created in the Prerequisite 4 \\(Deploy the ServiceNow IAM user \\(Stack\\) steps\\).\n\n1.  Sign in to the account where the ServiceNow user was created.\n2.  Search for IAM, then select Users &gt; servicenow-aict-user.\n\n3.  Select the **Security credentials tab**, then select **Create access key**.\n4.  Select **Application running outside AWS**, then select **Next**.\n\n5.  \\(Optional\\) Add a description tag, then select **Create access key**.\n6.  Save the credentials:\n\n    1.  Access Key ID: AKIA...\n    2.  Secret Access Key: wJal...\n    The Secret Access Key is only shown only once. Download the .csv file or save the value immediately.\n\n    **CLI Alternative:**\n\n    ```\n    aws iam create-access-key --user-name servicenow-aict-user\n    ```\n\n\n**Note:** An IAM user can have a maximum of two access keys. If two access keys already exist, delete one before creating a new one.\n\n**8. Setup CloudWatch Log Group and CloudTrail**\n\nThe connector queries CloudWatch Logs to retrieve Bedrock invocation counts per agent. CloudTrail captures the Bedrock data events and delivers them to the log group. Complete this step in each member account from which you want usage data.\n\nThis step is optional - complete it only if you want agent invocation counts. Asset discovery works without it.\n\n1.  Create the CloudWatch Log Group.\n2.  Search CloudWatch → Logs → Log groups → Create log group\n\n    1.  Log group name: /aws/bedrock/aict-invocations\n    2.  Retention: 90 days \\(recommended\\).\n    3.  Select **Create**.\n    **CLI Alternative**\n\n    ```\n    # Create\n    aws logs create-log-group --log-group-name /aws/bedrock/aict-invocations\n     \n    # Verify\n    aws logs describe-log-groups --log-group-name-prefix /aws/bedrock/aict-invocations\n    \n    ```\n\n    **Note:** If a log group already exists for this purpose, use its name in the connector configuration.\n\n3.  Create an IAM Role for CloudTrail to CloudWatch Logs delivery\n\n    CloudTrail requires permission to write events into the log group. Create a role that grants this permission.\n\n4.  IAM → Roles → Create role\n    1.  Trusted entity type: AWS service\n    2.  Service: CloudTrail\n    3.  Select **Next**.\n5.  Attach the following inline policy:\n\n    ```\n    {\n      \"Version\": \"2012-10-17\",\n      \"Statement\": [\n        {\n          \"Effect\": \"Allow\",\n          \"Action\": [\n            \"logs:CreateLogStream\",\n            \"logs:PutLogEvents\"\n          ],\n          \"Resource\": \"arn:aws:logs:*:*:log-group:/aws/bedrock/aict-invocations:*\"\n        }\n      ]\n    }\n    \n    ```\n\n6.  Role name: CloudTrailToCloudWatchLogsRole → Create role\n7.  Copy the Role ARN — required in Step 10, when configuring CloudWatch Logs delivery in the trail.\n8.  Create the CloudTrail. Search CloudTrail &gt; Trails &gt; Create trail\n9.  Trail settings:\n    1.  Trail name: servicenow-aict-bedrock-trail\n    2.  Storage location: Create a new S3 bucket or use existing.\n    3.  S3 bucket name: servicenow-aict-cloudtrail-logs-&lt;account-id&gt;\n10. CloudWatch Logs — Enable:\n    1.  Log group: /aws/bedrock/aict-invocations\n    2.  IAM role: CloudTrailToCloudWatchLogsRole \\(from Step 7\\)\n11. Select **Next** → Events\n    1.  Event type: Data events\n    2.  Uncheck Management events\n12. Configure data event selectors — add each of the following:\n\n    |**Data event source**|**Event type**|\n    |---------------------|--------------|\n    |Bedrock Agent Alias|AWS::Bedrock::AgentAlias|\n    |Bedrock Async Invoke|AWS::Bedrock::AsyncInvoke|\n    |Bedrock Inline Agent|AWS::Bedrock::InvokeInlineAgent|\n    |Bedrock Knowledge Base|AWS::Bedrock::KnowledgeBase|\n    |Bedrock Model|AWS::Bedrock::Model|\n    |Bedrock Session|AWS::Bedrock::Session|\n    |Bedrock Flow Alias|AWS::Bedrock::FlowAlias|\n\n13. Select **Next** &gt; Review &gt; Create trail\n\n**CLI Alternative:**\n\n```\n# Create trail\naws cloudtrail create-trail \\\\\n  --name servicenow-aict-bedrock-trail \\\\\n  --s3-bucket-name servicenow-aict-cloudtrail-logs-<account-id> \\\\\n  --cloud-watch-logs-log-group-arn arn:aws:logs:<region>:<account-id>:log-group:/aws/bedrock/aict-invocations \\\\\n  --cloud-watch-logs-role-arn arn:aws:iam::<account-id>:role/CloudTrailToCloudWatchLogsRole\n \n# Enable logging\naws cloudtrail start-logging --name servicenow-aict-bedrock-trail\n \n# Verify trail is active\naws cloudtrail get-trail-status --name servicenow-aict-bedrock-trail\n\n```\n\n**Note:**\n\nRepeat this step in each member account from which you want usage data. Note the log group name — enter it in the Log Group Names field of the connector configuration.\n\nBedrock data events are only logged when agents are invoked. If no invocations have occurred, the log group exists but is empty. Invocation counts populate after the first discovery run.\n\n**9. Verify Services**\n\n1.  Bedrock:\n    1.  Search \"Bedrock\" → Bedrock console loads\n    2.  CLI \\(example\\): aws bedrock list-foundation-models --region us-east-1\n2.  SageMaker:\n    1.  Search \"SageMaker\" → SageMaker console loads\n    2.  CLI \\(example\\): aws sagemaker list-models --region us-east-1\n3.  CloudWatch Logs:\n    1.  Search \"CloudWatch\" → CloudWatch → Logs → Log groups\n    2.  CLI \\(example\\): aws logs describe-log-groups --region us-east-1\n\n**AWS prerequisites for version 2.1.2**\n\nTo setup AWS instructions, see the [Automating AICT AWS Connector Setup Using the CloudShell Deployment Script \\[KB3138431\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB3138431) article in the Now Support Knowledge Base.\n\n## AWS Prerequisite Troubleshooting\n\n|**Error**|**Solution**|\n|---------|------------|\n|Access Denied \\(creating stack/StackSet\\)|Ensure your session has CloudFormation, IAM, and Organizations permissions in the relevant account.|\n|Stack fails with \"requires capabilities: \\[CAPABILITY\\_NAMED\\_IAM\\]\"|On the Review page, select the check box acknowledging that CloudFormation may create IAM resources.|\n|StackSet operation FAILED|Open the StackSet → Operations tab → view the failed stack instance. Common causes: SCP restrictions, name conflicts from a prior failed run.|\n|Trusted access not enabled|Enable trusted access between AWS Organizations and CloudFormation StackSets in the Management account \\(Prerequisite 3\\).|\n|StackSet has no deployment targets|Verify you selected Deploy to organization or provided a valid OU ID.|\n|Service unavailable in region|Use us-east-1; not all regions have all services.|\n|Can't see Secret Access Key|Delete the key and create a new one.|\n|Log group already exists|Use the existing group; skip Prerequisite 8 or reuse the name.|\n|Explicit deny in service control policy|An SCP is blocking the action on that account. Contact the Organization administrator.|\n\n## Data Mapping\n\nThe following table lists the data sources, the staging tables, and the target tables  CMDB CI classes and non-CMDB  classes where data is stored for a  AWS  project.\n\n<table id=\"table_jc1_m2r_l3c\"><tbody><tr><td>\n\nData Source\n\n</td><td>\n\nStaging Table\n\n</td><td>\n\nTarget Table\n\n</td></tr><tr><td>\n\nSGawsBedrockAIAssetDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_asset\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_system \\(routes to other staging tables\\)\n\n</td></tr><tr><td>\n\nSGawsBedrockAISystemDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_system\n\n</td><td>\n\nalm\\_ai\\_system\\_digital\\_asset\n\n</td></tr><tr><td>\n\nSGawsBedrockAIModelDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_model\n\n</td><td>\n\nalm\\_ai\\_model\\_digital\\_asset\n\n</td></tr><tr><td>\n\nSGawsBedrockAIToolDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_tool\n\n</td><td>\n\nsn\\_ent\\_ai\\_tool\n\n</td></tr><tr><td>\n\nSGawsBedrockAIPromptDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_prompt\n\n</td><td>\n\nalm\\_ai\\_prompt\\_digital\\_asset\n\n</td></tr><tr><td>\n\nSGawsBedrockAISbcompM2mDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_sbcomp\\_m2m\n\n</td><td>\n\nsn\\_ent\\_ai\\_system\\_subcomponent\\_m2m\n\n</td></tr><tr><td>\n\nSGawsBedrockAIUsageDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_bedrock\\_ai\\_usage\n\n</td><td>\n\nsn\\_ai\\_disc\\_ai\\_usage\n\n</td></tr><tr><td>\n\nSGAgentCoreDataSourceUtil \\(importAgentRuntimesByID\\)\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_agentcore\\_ai\\_system\n\n</td><td>\n\nalm\\_ai\\_system\\_digital\\_asset\n\n</td></tr><tr><td>\n\nSGAgentCoreDataSourceUtil \\(importCodeInterpretersByID, importBrowsersByID, importTargetsByID\\)\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_agentcore\\_ai\\_tool\n\n</td><td>\n\nsn\\_ent\\_ai\\_tool\n\n</td></tr><tr><td>\n\nSGAgentCoreDataSourceUtil \\(getAWSAgentCoreUsage\\)\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_agentcore\\_ai\\_usage\n\n</td><td>\n\nsn\\_ai\\_disc\\_ai\\_usage\n\n</td></tr><tr><td>\n\nSGSageMakerAIModelDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_sg\\_awssagemaker\\_model\n\n</td><td>\n\nalm\\_ai\\_model\\_digital\\_asset\n\n</td></tr><tr><td>\n\nSGSageMakerModelCardDSUtilSNC\n\n</td><td>\n\nsn\\_ai\\_disc\\_aws\\_sgc\\_sg\\_awssagemaker\\_model\n\n</td><td>\n\nalm\\_ai\\_model\\_digital\\_asset\n\n</td></tr></tbody>\n</table>"}}