Secrets Manager
The Secrets Manager provides secure storage for sensitive values your project needs: API keys, tokens, database credentials, and configuration secrets that should not be hardcoded in your application.

Why Secrets Manager Matters
Hardcoding credentials in application code creates security vulnerabilities and operational friction. Every key rotation requires a code change, secrets leak into version control, and access becomes impossible to audit. The Secrets Manager centralizes credential storage with proper security controls, separating sensitive configuration from your codebase.
With Secrets Manager, you can:
Store credentials encrypted at rest with project-level isolation
Reference secrets in workflows and pipelines without exposing values in code
Rotate credentials without redeploying your application
Restrict access to users with appropriate permissions
Secret Structure
Each secret consists of a name and one or more key-value pairs. This structure allows grouping related credentials under a single identifier. For example, a secret named database-config might contain keys for host, port, username, and password.
Secret Values are hidden by default. Once saved, you cannot view them in plain text again, you can only delete or replace them.
Using Secrets Manager
Last updated
Was this helpful?

