prometheus / prometheus/exporter-toolkit
Add support for certificate managers/keystores
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 311
- Forks
- 109
- Avg merge
- 3d 59m
- Merged PRs (30d)
- 6
Description
Hello,
It could be very usefull and compliant with lot of security levels to add the support of certificate managers/keystores as plugin or embded providers.
As common keystores we could start with :
- jks (java keystore)
- pfx (alias PKCS#12, windows certificate export format)
- Windows certificate store (where are stored already installed certificates)
- AWS cloud HSM
- Azure Key Vault
I know we could delegate it to a reverse proxy with already these capabilities, but for a full in transit encryption compliance it can be a nightmare.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the exporter-toolkit package and clarifying the proposed plugin or embedded-provider scope with maintainers. Compare the requested JKS, PKCS#12, Windows certificate store, AWS Cloud HSM, and Azure Key Vault support, then define which providers and acceptance criteria are in scope before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, java
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100