Oracle Cloud Infrastructure Secret Management vs Secrets Manager

Oracle Cloud Infrastructure Secret Management stores, retrieves, rotates, and manages credentials used by applications and cloud environments. It supports database passwords, access tokens, third-party API keys, SSH private keys, application configuration secrets, and OAuth2 or JWT signing credentials. Administrators and applications can access secrets through APIs, SDKs, the CLI, and OCI Console. OCI Vault keys encrypt secrets, while OCI manages encryption, decryption, access control, and audit logging; OCI IAM policies provide granular permissions. Automatic rotation can run at intervals from one to 12 months and integrates with Autonomous AI Database and OCI Functions. Secrets can be replicated to as many as three destination regions, where replicas are read-only and inherit changes from the source. A tenancy can contain up to 5,000 secrets, with up to 30 active versions and 30 versions pending deletion per secret. The service is aimed at applications and cloud environments that need centrally managed secrets rather than credentials embedded in source code or configuration files. It is listed as free, though no price is provided.

Secrets Manager is a free, open-source, self-hosted system for storing application secrets in encrypted form, managing them through a web interface, and injecting them into processes with a command-line tool. Users organize secrets by organization, project, and environment, import.env files, edit or reveal values, keep versions, roll back, and soft-delete entries. The `secrets run` command supplies environment secrets to a child process and its descendants without creating a.env file. Documented workflows cover Node.js, Python, npm, and Next.js; CI or deployment can use an API URL, token, and environment ID. User and service-account grants can be scoped to projects or environments, and revealing values requires explicit permission. AES-256-GCM envelope encryption uses a separate data key per value, while plaintext values are not stored in the database. Audit events include secret reveals, and values are withheld if audit writing fails. Docker Compose starts PostgreSQL, Redis, backend, and frontend; local Kubernetes manifests are also provided. A user-generated master key is mandatory and lost keys make secrets unrecoverable. The repository is MIT licensed.