Overview
The vault integration provides:- Automated Key Synchronization: Connect to your existing vault infrastructure and sync all API keys automatically
- Periodic Key Management: Regular synchronization ensures deprecated and archived keys are properly managed
- Multi-Vault Support: Compatible with HashiCorp Vault, AWS Secrets Manager, Google Secret Manager, and Azure Key Vault
- Zero-Downtime Operations: Keys are synced without interrupting your running services
Supported Vault Systems
HashiCorp Vault
Connect to your HashiCorp Vault instance for centralized secret management.AWS Secrets Manager
Integrate with AWS Secrets Manager for cloud-native secret storage.Google Secret Manager
Use Google Cloud’s Secret Manager for secure key storage.Azure Key Vault
Connect to Azure Key Vault for Microsoft cloud environments.Key Synchronization
Automatic Sync Process
Bifrost automatically synchronizes keys from your vault at regular intervals:- Discovery: Scans the configured vault paths for API keys and virtual keys
- Validation: Verifies key format and accessibility
- Sync: Updates Bifrost’s internal key store with new and modified keys
- Deprecation: Identifies and archives keys that have been removed from the vault
- Notification: Logs sync status and any issues encountered
Sync Configuration
Configure synchronization behavior to match your operational requirements:Configuration Options
| Option | Description | Default |
|---|---|---|
sync_interval | Time between sync operations | 300s |
sync_paths | Vault paths to monitor for keys | ["bifrost/*"] |
auto_deprecate | Automatically deprecate removed keys | true |
backup_deprecated_keys | Backup keys before deprecation | true |
Key Management Lifecycle
Key States
Keys in Bifrost can have the following states:- Active: Currently in use and available for requests
- Deprecated: Marked for removal but still functional
- Archived: Removed from active use but retained for audit purposes
- Expired: Keys that have exceeded their validity period
Deprecation Process
When keys are removed from the vault:- Detection: Next sync cycle identifies missing keys
- Grace Period: Keys enter deprecated state with configurable grace period
- Notification: Administrators are notified of pending deprecation
- Archive: Keys are moved to archived state after grace period expires
Security Considerations
Authentication
- Vault Tokens: Use time-limited tokens with minimal required permissions
- IAM Roles: Leverage cloud provider IAM roles for secure authentication
- Certificate-based Auth: Support for mutual TLS authentication where available
Encryption
- Transit Encryption: All communication with vault systems uses TLS
- At-Rest Encryption: Keys are encrypted in Bifrost’s internal storage
- Key Rotation: Automatic detection and handling of rotated vault credentials

