Connecting AWS and SailPoint CIEM

Once you have configured your Amazon Web Services (AWS) account, you can connect it to display the effective access users have on collected AWS cloud resources.

If you are only using AWS Identity Center, you will configure the CIEM AWS connector. If you plan to govern IAM users and groups, you will configure the AWS connector.

To display this data, you must use both the AWS and SailPoint CIEM AWS connectors.


SailPoint CIEM AWS connector	Works with your AWS connector to collect cloud resource data and display the total access an identity has to your cloud systems.
AWS connector	Allows you to manage your AWS IAM users and groups in Identity Security Cloud. If your organization has licensed a SailPoint cloud management solution, it will also gather data about the cloud access granted to users through policies, roles, organization unit, and AWS accounts.

FedRamp Limitations

SailPoint CIEM FedRamp customers can register a maximum of 650 AWS member accounts.

You may connect your AWS and SailPoint CIEM AWS sources in any order.

After you've connected and aggregated your cloud accounts and entitlements, you will mark your IAM and AWS Identity Center (if using) entitlements as cloud enabled. This will allow you to view the cloud access granted through entitlements and include those entitlements in certification campaigns.

Using the AWS Connector

Follow the SailPoint Connector guide to connect your AWS IAM governance source.

After a successful test connection, you will aggregate and mark the entitlements that grant cloud access.

Using the SailPoint CIEM AWS Connector

The SailPoint CIEM AWS source pulls daily data about the cloud resources users can access. Users can be IAM, AWS Identity Center, Entra IDP, or Okta IDP.

You can use the information from verifying your configuration to register SailPoint CIEM:

Go to Admin > Connections > Sources > Create New.
Find the CIEM AWS source type and select Configure.
Enter a source name.
Enter a description for your source.
In the Source Owner field, begin typing the name of an owner. Matches appear after you type two letters.
(Optional) Select a governance group for source management.
Select Connection Settings.
Enter the Role ARN for the role generated when creating an IAM role. If you are using AWS Organizations, the role ARN should correspond to the management account’s role ARN.
The External ID field is autopopulated. You will copy the external ID to use when configuring AWS.
(Optional) Enter the CloudTrail ARN for an organization or individual member account. You can add up to 150 CloudTrail ARNs, separated by commas.
- Enter the AWS Account ID where the CloudTrail bucket is hosted.
If the source uses a single account (as opposed to the organization account) select the Single Account toggle.

Note

Identity Center accounts cannot be aggregated using a single account. To aggregate identity center users, ensure Single Account is not selected.
If you are using the Identity Center directory as your identity source, as opposed to Active Directory or another external IdP, select the Provision Identity Center toggle to enable provisioning of Identity Center accounts.
Important
- It is not recommended to enable both Single Account and Provision Identity Center because identity center accounts won't be aggregated or have entitlements provisioned.
- Due to limitations with the IdentityStore API, password provisioning and enabling and disabling accounts are not supported.
Required Provisioning String

To use Identity Store provisioning, ensure the CIEM AWS connector has the PROVISIONING feature string. You can check if provisioning is enabled using the Developer Tools or GET the source's endpoint to find:
```
"features": [
    "PROVISIONING"
],
```
If it is not enabled, you can use the update-source API to set and validate this using the following payload:
```
{
    "op": "add",
    "path": "/features",
    "value": "PROVISIONING"
}
```
Select Save.
Select Review and Test.
Review the configuration details and select Test Connection. A successful test is required for SailPoint CIEM to gather data for this source.
Notes
- CloudTrail ARNs are tested asynchronously. If a CloudTrail cannot be connected, an error will display in the event logs.
- If the test connection fails, you can use the Search query name:“Test_connection Source Failed” for more information.
(Optional) Enable native change detection. You can monitor your AWS Identity Center Groups and AccountPermissionSet entitlement attributes for changes made outside of Identity Security Cloud, as well as non-entitlement attributes.
Select Save.

After a successful test connection, you can set the source scope or move on to managing your cloud accounts and entitlements.

Setting Source Scope

By default, SailPoint CIEM reads and automatically discovers changes to your cloud infrastructure, which are displayed in the Cloud Scopes section of your CIEM AWS source configuration. You can choose to exclude scopes to prevent SailPoint CIEM from including data for those accounts.

To change the scope of your included source data:

In the CIEM AWS source, select Cloud Scopes under Aggregation and Provisioning.
Use the checkboxes to change which accounts are included. Removing a scope disables Auto-Include Scopes.
Select Save.

SailPoint CIEM will now only read and include data from your selected scopes. When Auto-Include Scopes is disabled, new and deleted accounts in your cloud system will be detected, but SailPoint CIEM will not automatically include data from new scopes until you select the accounts individually or reenable Auto-Include Scopes.

Notes

You can search for scopes as well as filter by selected and unselected scopes.
The Last Refreshed time is when changes to your source inventory were last detected by SailPoint CIEM. This is separate from aggregation.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.