Getting Started with SecureVault

Initialize and configure Aevum Zenth SecureVault to begin managing encrypted secrets, keys, and sensitive data across your enterprise infrastructure with zero-knowledge architecture.

â„šī¸
New to SecureVault?

SecureVault is part of the Zenth Cloud ecosystem. If you don't have an Aevum Zenth account, create one here or contact your enterprise administrator.

Prerequisites

Before integrating SecureVault, ensure your environment meets the following requirements:

Installation

Install the SecureVault SDK for your preferred language:

NPM
Pip
Go
Cargo
Shell
npm install @aevumzenth/securevault
Shell
pip install aevum-securevault
Shell
go get github.com/aevumzenth/securevault-go/v2
Shell
cargo add aevum-securevault

Quick Start

Follow these steps to initialize SecureVault and store your first encrypted secret.

1
Import and Initialize

Create a new SecureVault client instance using your API credentials.

TypeScript
import { SecureVault } from '@aevumzenth/securevault';

const vault = new SecureVault({
  apiKey: process.env.AEVUM_API_KEY,
  projectId: 'proj_zenth_8x92k',
  region: 'us-east-1' // Optional: defaults to auto-detect
});
2
Create an Encrypted Secret

Use the storeSecret method to encrypt and store data. The SDK handles client-side encryption before transmission.

TypeScript
const response = await vault.secrets.store({
  name: 'db-connection-string',
  value: 'postgresql://user:password@host:5432/db',
  tags: ['production', 'database'],
  rotation: {
    enabled: true,
    intervalDays: 90
  }
});

console.log(`Stored secret with ID: ${response.id}`);
// Output: Stored secret with ID: scret_zenth_4a7f9x2...
3
Retrieve and Decrypt

Fetch the secret by name or ID. The SDK automatically decrypts the value using your Z-Key context.

TypeScript
const secret = await vault.secrets.get('db-connection-string');

console.log(secret.value);
// Output: postgresql://user:password@host:5432/db
âš ī¸
Security Notice

Never hardcode API keys in your source code. Use environment variables or a secure secrets manager for your API credentials. SecureVault is designed to protect your data, not your credentials.

Configuration Options

The SecureVault client accepts several configuration options during initialization:

Option Type Description
apiKey string Your Aevum Zenth API key. Required unless using Z-Service Token.
projectId string Target project ID for scoped operations.
region string Data residency region. Defaults to auto-detection based on latency.
timeout number Request timeout in milliseconds. Default: 5000.

Next Steps

Now that you've completed the quick start, explore these resources to deepen your integration:

🚀
Need Help?

Join the Aevum Zenth Developer Community or contact secure-support@aevumzenth.io for enterprise assistance.