Amplitude

Amplitude is a product analytics platform. It helps businesses to track visitors with the help of collaborative analytics.

In order to integrate Amplitude to Relyance AI, you will need an API key, Secret Key, and SCIM Key (optional). The SCIM Key is an optional parameter based on the subscription tier. This allows the integration to hit SCIM endpoints.

In Amplitude:

1. Login to your Amplitude account.
2. Navigate to the Settings menu in the bottom left-hand side.
3. Under ORG SETTINGS select the Projects tab.
4. A list of all projects will be displayed.
5. Navigate to the project that you want to inspect using Relyance AI and select it.
6. Under General tab of your respective project, you will find two fields named API Key and Secret Key respectively. Copy these keys to be used in Relyance AI.
7. (SCIM Optional) In the ORG SETTINGS Menu select Access & SSO Settings.
8. (SCIM Optional) Find the Provisioning Settings section and ensure the SCIM Provision Enabled checkbox is enabled.
9. (SCIM Optional) Click Generate SCIM Key (or Regenerate SCIM Key) and copy the SCIM Key to be used in Relyance.

Note: If this key is being used elsewhere. Please use the existing key.

In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the Amplitude integration card and click on it.
5. Click on the Add Connection button on the top right.
6. Provide a meaningful name for the integration and click on the Add button.
7. In the Overview section, select the integration features you wish to enable for the integration, review the Scope and Permission, and Endpoint details and click on Continue. For more details, see Integration Features.
8. In the Connection section, provide the appropriate values and click on Continue,
   • Connection Name: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by Discovery Source across the Inventory, Visual Maps, Assets, and Data Flow Analysis pages.
   • Rescan Frequency: This property allows you to configure how often Relyance executes scans against this Vendor connection.
   • Business Atlas Associations (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the Select Associations dropdown — the wizard will not advance past this step without one. For more details, see Business Atlas.
9. In the Authentication section, provide the following information retrieved from the Amplitude section and click on Authenticate.
   • API Key
   • Secret Key
   • SCIM Key (Optional - Requires Enterprise Plan)
10. This step applies only if the Data Inspection check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on Continue,
    • Minimum Confidence Level: This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.
11. Review the configuration summary from the Completion section and click on Finish.
12. Confirm the integration Status reflects Connected.

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 feature you enabled returns nothing. Some scopes belong to a feature rather than to the connection: Data subject requests needs Default. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. A credential rotated at the vendor is not picked up here. API Key, Secret Key and SCIM Key (Optional - Requires Enterprise Plan) 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.
3. Check the address fields before suspecting the credentials. EU instance identifies 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" "amplitude" {
  vendor = "amplitude"
  name   = "<your connection name>"

  auth = {
    method = "api-key"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      eu_instance = "false"
      api_key = var.amplitude_api_key
      secret_key = var.amplitude_secret_key
      scim_key = var.amplitude_scim_key
    }
    secrets_wo_version = 1
  }

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