OpenID Connect (OIDC)
DataChain Studio can use OpenID Connect to access cloud resources securely, without requiring manual configuration of static credentials.
To use OIDC, first follow the cloud configuration instructions and then the Studio configuration instructions.
Cloud configuration
Generic configuration details
-
OpenID Connect Discovery URL: https://studio.datachain.ai/api/.well-known/openid-configuration
-
Subject claim format:
credentials:{owner}/{name}where{owner}is the name of the DataChain Studio user or team owning the credentials, and{name}is the name of the DataChain Studio credentials.
Terraform examples
The following Terraform examples illustrate how to configure the supported cloud providers, granting DataChain Studio access to object storage resources through OpenID Connect. Update the fields as described below and then apply the Terraform configuration. Make note of the outputs of terraform apply, since you will need to enter those for Studio configuration.
Replace the sample credentials:example-team/example-credentials subject claim condition. Replace example-team with the Studio user or team owning the credentials, and replace example-credentials with any name you want to use for those credentials. This name must match what you enter during Studio configuration.
Amazon Web Services
Google Cloud
Studio configuration
Create new credentials and configure them as follows:
- Choose an adequate OIDC variant on the provider field; e.g. Amazon Web Services (OIDC).
- Enter the name for the credentials. This must match the name used during cloud configuration.
- Fill the provider-specific fields with the outputs from
terraform apply.
Troubleshooting
If you encounter issues with OIDC setup:
- Verify that the subject claim format matches exactly
- Check that the Terraform configuration has been applied successfully
- Ensure that the credential names match between cloud configuration and Studio configuration
- Verify that the workload identity pool and provider are configured correctly
For more help, see our troubleshooting guide.