---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure access based on trusted accounts with credentials

# Configure access using temporary credentials based on trusted AWS accounts with AWS credentials {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 Minuten Lesedauer

Configure the trusting account whose resources need to be accessed, to rely on the trusted account using the Identity and Access Management (IAM) role.

## Vorbereitungen

* Familiarize yourself with the Amazon documentation on [Creating a role to delegate permissions to an IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user.html).
* Decide which AWS account is going to be the trusted account. You use the trusted account to configure temporary credentials for Cloud Discovery using IAM roles. The trusted account that you use to access other accounts using IAM roles is referred to as an accessor account.
* If you're setting up a trust chain where a member account trusts a management account, and the management account trusts an accessor account, verify that you've configured the member account to trust the management account. For more information, see [Configure access using temporary credentials for trusting AWS member accounts in management-accessor trust chain](https://servicenow-prod.fluidtopics.net/15m9TBv6QW6sJ4OYdW6A1w "Configure access for AWS member accounts by using a trust chain from the accessor through the management account.").
* Confirm that Discovery Admin Workspace is using at least version 1.10.0. The DiscoveryCloud Service Accounts navigation module isn't available with earlier versions. To access Cloud Service Accounts with an earlier version, enter in the navigation filter: <kbd class="ph userinput">cmdb_ci_cloud_service_account.list</kbd>.

{#configure-iam-role-aws-account__ul_hr2_gf5_zfc}  
Role required:

* For Cloud Discovery: discovery_admin
* For Cloud Provisioning and Governance: admin or sn_cmp.cloud_admin
{#configure-iam-role-aws-account__ul_n3k_vyz_g5b}

## Warum und wann dieser Vorgang ausgeführt wird

During this configuration, you create an IAM role for the trusting account, and then configure the trusted service account for the trusting account at ServiceNow AI Platform. Finally, you associate the IAM role you created for the trusting account with the trusting account itself.
Abbildung : 1. Setting up any AWS account to rely on a trusted account with AWS credentials   

## Prozedur

1. Create an IAM role for the trusting account and configure the trust relationship between the user assuming this role and the trusted (accessor) account.
   1. Log in to the trusting account on the AWS Management Console.
   2. Create and configure the IAM role specifying the trusted (accessor) account ID in the Account ID field.  
      For information on creating AWS roles, see the [Amazon documentation](https://docs.aws.amazon.com/).
   3. On the Summary page for the IAM role, select the Trust Relationships tab.
   4. Select Edit trust relationship.  
      The Edit Trust Relationship page opens showing the policy document.
   5. Set the AWS parameter to the full user ARN of the trusted (accessor) account.  

      <br />

   6. Verify that the Action value is set to sts:AssumeRole.
   7. Select Update Trust Policy.
   {#configure-iam-role-aws-account__substeps_bh2_zz2_kpb}
2. On the ServiceNow AI Platform, configure the trusted service account.
   1. Navigate to AllDiscoveryCloud Service Accounts.
   2. Selelct New.
   3. On the form, fill in the fields.  
      For a description of the field values, see [Create AWS service accounts](https://servicenow-prod.fluidtopics.net/uTa4K3UBhqLrbRzrstyZrA "Create AWS service accounts on the ServiceNow AI Platform to access your AWS account during AWS discovery.").
   4. Select Submit.
   {#configure-iam-role-aws-account__substeps_eq5_mg5_zfc}
3. On the ServiceNow AI Platform, configure the trusting service account.
   1. Navigate to AllDiscoveryCloud Service Accounts.
   2. Select New.
   3. In the Accessor account field, enter the name of the trusted account.
   4. On the form, fill in the remaining fields.  
      For a description of the field values, see [Create AWS service accounts](https://servicenow-prod.fluidtopics.net/uTa4K3UBhqLrbRzrstyZrA "Create AWS service accounts on the ServiceNow AI Platform to access your AWS account during AWS discovery.").
   5. Select Submit.
   {#configure-iam-role-aws-account__substeps_dkg_1h5_zfc}
4. On the ServiceNow AI Platform, assign the AWS IAM role to the trusting account, using the relevant form, based on the relationship to the trusted account.

   | Trusted account type | Steps |
   | Management account | 1. Navigate to AllCloud Provisioning and GovernanceOrganization Access ParametersAWS Org Assume Role Parameters. 2. Select New. 3. On the form, configure only the following fields for the trusting member account: {#configure-iam-role-aws-account__aws-org-assume-member-trusts-management__entry__2} | Field | Definition | |-|-| | Access role name | Name of the IAM role created for the trusting account. * If IAM roles are the same across all member accounts: Enter the full ARN using an asterisk (\*) as a wildcard for the account ID in the format: <kbd class="ph userinput">arn:aws:iam::*:role/MemberRoleName</kbd>. For example: <kbd class="ph userinput">arn:aws:iam::*:role/SN_MEMBER_ACCOUNT_ROLE</kbd>. * If IAM roles are different across member accounts: Enter the full ARN of the specific IAM role for each member account in a separate entry. {#configure-iam-role-aws-account__ul_njf_fxl_bgc} | | Cloud service account | Name of the trusting account for which you are providing access using the IAM role. * If IAM roles are the same across all member accounts: Enter the management account name. * If IAM roles are different across member accounts: Enter each member account in a separate entry. {#configure-iam-role-aws-account__ul_gvl_txl_bgc} | [Tabelle : 1. Cloud Service Account AWS Org Assume Role Params form] {#configure-iam-role-aws-account__aws-org-assume-member-trusts-management} 4. Select Submit. {#configure-iam-role-aws-account__ol_msk_kk5_zfc} |
   | Member or discrete account | 1. Navigate to AllCloud Provisioning and GovernanceOrganization Access ParametersAWS Cross Assume Role Parameters. 2. Select New. 3. On the form, configure only the following fields for the trusting account: {#configure-iam-role-aws-account__table_vx5_qj5_zfc__entry__2} | Field | Description | |-|-| | Access role name | Name of the IAM role created for the trusting account. | | Cloud service account | Name of the trusting account for which you are providing access using the IAM role. | [Tabelle : 2. Cloud Service Account AWS Cross Assume Role Params form] {#configure-iam-role-aws-account__table_vx5_qj5_zfc} 4. Select Submit. {#configure-iam-role-aws-account__ol_nmz_n35_zfc} |
   |-|-|

   {#configure-iam-role-aws-account__choicetable_g1z_335_zfc}
{#configure-iam-role-aws-account__steps_skv_jm4_h5b}

## Nächste Maßnahme

Verify that ServiceNow applications can access the trusting service account using the IAM role:

1. Navigate to AllDiscoveryCloud Service Accounts.
2. Select the trusting AWS service account.
3. Under Related Links, select Create Discovery Schedule.
4. In the Discovery Manager Cloud Discovery page, select Test Account.
   * If the connection is successful, a message displays indicating the account validation is successful.
   * If the connection isn't successful, an error message displays indicating the cause of failure.
   {#configure-iam-role-aws-account__ul_aq2_5yt_2gc}
{#configure-iam-role-aws-account__aws-testing-credentials}