Docs › Your data
Cloud databases without passwords
Azure SQL and Azure Database for PostgreSQL or MySQL, Amazon RDS and Aurora, and Google Cloud SQL can all let a data source sign in without a stored password. Your cloud trusts your workspace's own identity, and only for that one data source, so there is no long-lived secret anywhere.
Plan availability Part of the Data sources add-on, on the Plus and Ultimate plans.
How it works#
Every workspace has its own identity issuer, an address like https://id.<our domain>/ws/<number>. Each data source has its own subject, ifp:ws:<workspace>:ds:<data source>. Your cloud is told to trust exactly that issuer and that subject. A refresh gets a token that lasts five minutes, your cloud exchanges it for a database token, and that is used to sign in.
Because the trust names your workspace and that data source, nobody else can point their own data source at your database and be let in.
Set it up#
- Add a data source and choose Cloud database, without a password, then your cloud.
- Enter the server, database and the objects to read.
- On the sign-in step, the wizard shows the workspace's issuer and the data source's subject (both given by the service, never typed), and generates the setup for your cloud with them filled in. Run it in your own account.
- Enter the values it prints (below), and choose Seal and test. There is no password to enter.
Azure#
- A user-assigned managed identity with a federated credential for the issuer and subject, audience
api://AzureADTokenExchange(a Bicep or ARM snippet). - In the database,
CREATE USER [<identity>] FROM EXTERNAL PROVIDERandGRANT SELECTon the objects (or the PostgreSQL / MySQL equivalent the wizard shows). - Enter the tenant ID and the identity's client ID.
AWS#
- An IAM OIDC identity provider for the issuer, and a role whose trust policy requires the subject and audience
sts.amazonaws.com, allowedrds-db:connecton one database user (CloudFormation or Terraform). - A database user granted
rds_iam. - Enter the role ARN, the region and the database user.
Google Cloud#
- A workload identity pool and OIDC provider for the issuer, with a condition on the subject, and a service account it may impersonate with
roles/cloudsql.clientandroles/cloudsql.instanceUser(gcloud or Terraform). - An IAM database user for the service account.
- Enter the provider's audience and the service account's email.
Network access#
- Public endpoint and firewall. Add our published addresses to the database's firewall. TLS and the identity still apply.
- Azure Private Link. For Azure SQL, PostgreSQL and MySQL flexible server, choose Private Link in the wizard and paste the server's resource ID. Approve the pending private endpoint connection in the Azure portal (its message names your workspace), then seal the credential again with the private address the app shows.
- A gateway in your virtual network, for private AWS and Google Cloud databases. See Install and pair a gateway.
Removing access#
Remove the federated credential, the role trust or the workload identity binding in your cloud, and the data source can't sign in from the next refresh on. Existing tokens expire within their lifetime.
Plan limits summary#
| Feature | Free | Mini | Plus | Ultimate |
|---|---|---|---|---|
| Cloud databases without a password (part of the Data sources add-on, $30 a month per workspace) | No | No | With the add-on | With the add-on |
| Azure Private Link | No | No | With the add-on | With the add-on |