3rd party secrets-engine plugin backends

Open
#534 15 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
aws, azure, google-cloud

Research direction

No files, tests, or entry points are identified. Review the candidate backend list and voting comments first; completion would require a selected backend and agreed implementation scope, which this issue does not yet specify.

Written by the indexing model from the issue text.

Description

The secrets engine resolves se://<id> references through plugins. Below are candidate backends we're considering, grouped by where they fit in a user's workflow.

Locally-usable backends

Routinely used from a developer's machine, personal/team password managers, or self-hostable secret servers a developer authenticates to with a token.

  • 1Password (ships June 8, 2026 / Docker Desktop 4.77.0 delayed -> 4.78.0)
  • Bitwarden (with Vaultwarden as a self-hosted, API-compatible option)
  • LastPass
  • HashiCorp Vault
  • OpenBao

Cloud-deployment backends

Primarily used by workloads running in a cloud, reading secrets provisioned in that same cloud (IAM role, managed identity, workload identity).

  • AWS Secrets Manager
  • AWS SSM Parameter Store
  • Azure Key Vault
  • Google Cloud Secret Manager

Vote for the plugin you want most scroll down and react with 👍 on the comment for that backend. The more reactions a backend gets, the sooner it moves up our list.

Don't see your secret store? Drop a new comment with the backend you'd like supported and a short note on how you use it (personal workstation, CI, production workloads, …).

Dominant language
Go
Stars
91
Forks
16
Avg merge
9h 3m
Merged PRs (30d)
24

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/secrets-engine

All issues in docker/secrets-engine

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.