Connect your secrets manager to DataRaven for zero-knowledge credential management with BYOV (Bring Your Own Vault).
DataRaven’s Bring Your Own Vault (BYOV) architecture ensures your cloud credentials never touch
our infrastructure. Connect your existing secrets manager, map fields to vault references, and
DataRaven resolves credentials in-memory at transfer time — then immediately discards them.
BYOV is optional. DataRaven also provides built-in secret storage powered by AWS SSM Parameter
Store SecureString. You can store credentials securely without connecting an external vault.
Self-hosted vaults are not supported at this time. Only managed/cloud-hosted instances of
1Password, Doppler, and Infisical are supported.
Go to Settings → Vault Connections → Add Connection, select your provider, and provide a
scoped access token. DataRaven encrypts the token and stores it in AWS SSM Parameter Store —
it’s never returned in API responses.
2
Create secrets with field mappings
Create a secret that maps DataRaven field names (like access_key_id) to references in your
vault (like op://DevOps/AWS-Prod/access_key_id). Each mapping tells DataRaven where to find
the credential at runtime.
3
Reference secrets in locations
When configuring a storage location, select your vault-backed secret instead of entering
credentials directly. The location will resolve credentials from your vault every time it’s
used.
4
Zero-knowledge resolution
At execution time, DataRaven authenticates to your vault, resolves the mapped credentials into
memory, performs the transfer operation, and immediately discards them. Nothing is cached or
persisted.
Open your Infisical project → Project Settings → Access Control
Go to Machine Identities → Create
Enable Universal Auth for the identity
Generate a client ID and client secret
Grant the identity read access to the project and environment containing your credentials
Copy the project ID from Project Settings → General
Infisical does not support token rotation through the API. To rotate credentials, you must delete the vault connection and create a new one with updated Machine Identity credentials.
Click Rotate Token from the connection detail page. Enter the new token and DataRaven will replace the encrypted token in storage. All secrets using this connection will immediately use the new token — no other changes needed.
Token rotation is not available for Infisical connections. To rotate credentials:
Create a new Machine Identity in Infisical (or regenerate the client secret)
Delete the existing vault connection in DataRaven
Create a new vault connection with the updated credentials
Re-link any secrets that referenced the old connection
Vault tokens are encrypted and stored in AWS SSM Parameter Store SecureString parameters.
They are never stored in DataRaven’s database.
Never exposed
Tokens and credentials are never returned in API responses. The API only surfaces a vault
reference ID.
In-memory only
Cloud credentials are resolved in-memory at execution time and immediately discarded after
the operation completes.
Audit logged
All vault operations — connections, tests, rotations, and secret resolutions — are logged for
audit purposes.
Follow the principle of minimum privilege when creating vault tokens. Grant read-only access
to only the specific vaults, projects, or environments that DataRaven needs.