Store kms client with each master key
Open
Nobody has claimed this yet.
enhancement
priority/low
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Follow up on #149 : instead of recreating the kms service every time, we should cache it with the master key it belongs to. We could even optimize further by creating one client per region+role.
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 reading issue #149 and tracing where the KMS service is recreated for each master key. Determine how master keys identify their region and role, then evaluate the proposed per-key cache and possible region-plus-role client reuse. Done means repeated operations reuse the intended clients without changing key-management behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100