SecretVault: One Interface to Rule All Your Cloud Secrets in .NET 9
SecretVault is a new .NET 9 library that provides a unified interface for managing secrets across multiple cloud providers, reducing dependency on provider-specific SDKs and enabling easier secret rotation, caching, and error handling. It supports AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, and Google Cloud Secret Manager through modular NuGet packages. The library integrates with ASP.NET Core for dependency injection, configuration, and health checks, allowing consistent secret access in both development and production. By abstracting provider differences, SecretVault aims to eliminate secret sprawl and vendor lock-in.
- ▪SecretVault offers a single interface, ISecretManager, to access secrets from AWS, Azure, HashiCorp, and Google Cloud without changing application code.
- ▪It includes built-in features like caching, fallback chaining, secret rotation, and normalized error handling across providers.
- ▪The library integrates with ASP.NET Core for DI, IConfiguration, and health checks, enabling secrets to be used like standard configuration values.
- ▪SecretVault is distributed as modular NuGet packages, allowing developers to install only the providers they need.
- ▪It requires .NET 9 initially, leveraging modern C# features, with potential future support for .NET Standard 2.0 based on demand.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3139981) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Naimul Karim Posted on Apr 29 • Originally published at github.com SecretVault: One Interface to Rule All Your Cloud Secrets in .NET 9 #dotnet #csharp #aws #azure Every .NET project that touches the cloud eventually runs into the same problem: secret sprawl. You start with AWS Secrets Manager. Then a new service needs Azure Key Vault. Someone spins up a HashiCorp Vault.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
