Terminology Index

Glossary

2953 terms

Open concept maps
M
32

Microservices Secrets

Managing secrets, API keys, database credentials, tokens, that many microservices need, in a way that keeps them out of code and configuration, distributes them safely, and rotates them centrally.

Microservices architectures create a secrets-management challenge: many small services each need credentials, and naive approaches (hardcoded secrets, secrets in manifests, shared static keys) lead quickly to leaks at scale. Sound microservices-secrets practice uses central vaults or KMS, short-lived dynamically issued credentials, the external-secrets pattern, and least-privilege scoping per service. It is a foundational cross-cutting concern for securing microservices and avoiding the credential sprawl that otherwise comes with the architecture.

Introduced in: Cloud-Native Security

Examples

  • Each microservice pulling credentials from a central vault at startup.
  • Issuing short-lived, scoped credentials per service rather than static keys.
  • Using the external-secrets pattern to keep plaintext out of manifests.