Satori

Satori Data Security Platform helps security and engineering teams streamline data access by automating access controls, security and compliance requirements across their data infrastructure.

To connect Satori with Relyance AI you will need an Account Id, a Service Account Id and Secret.

1. Login to your Satori account.

2. Select Settings at the top right corner.

3. Refer to User Management in the left-side menu.

4. Go to the Service Accounts tab.

   • Create an Account with Reader permissions.
   • The Service Account Id and Secret will be generated. Save this information.

   

   

5. Go to Account Settings in the-left side menu.

   • Copy the Account Id under the Basic Settings tab.

   

In the Relyance AI application

1. Login to your Relyance AI account.

2. Navigate to the Settings Menu in the bottom left-hand side.

3. Select Integrations.

4. Search for Satori and click it to open its connections.

5. Scroll down and select Custom under Create Connection.

   • Paste the Account Id, Service Account Id and Service Account Secret into the respective fields.

   

6. Click Authenticate.

7. Congratulations! You are now connected to Satori.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. A credential rotated at the vendor is not picked up here. Account ID, Service Account ID and Service Account Key are stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. Check the address fields before suspecting the credentials. Account ID and Service Account ID identify which tenant, region or host to talk to. A wrong value there fails authentication and looks exactly like a bad secret.

Authentication methods and fields

Pick one of these under Authentication Method on the connection wizard's Authentication step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

resource "relyance_integration_connection" "satori" {
  vendor = "satori"
  name   = "<your connection name>"

  auth = {
    method = "service-account"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      ACCOUNT_ID = var.satori_account_id
      SERVICE_ACCOUNT_ID = var.satori_service_account_id
      SERVICE_ACCOUNT_KEY = var.satori_service_account_key
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}