Cache sops AWS role assumption locally and re-use it
Open
Nobody has claimed this yet.
area/keyservice
enhancement
keyservice/awskms
priority/low
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
If an AWS role is configured within your sops config like so:
sops:
kms:
- arn: arn:aws:kms:us-east-1:656532927350:key/920aff2e-c5f1-4040-943a-047fa387b27e
role: arn:aws:iam::927034868273:role/sops-dev-xyz
every time sops runs it will assume this role, even though the STS token could be cached and re-used.
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
No files or tests are named. Start by locating the AWS role-assumption path used for KMS entries with a configured role, then inspect how STS credentials are obtained and stored. Done means repeated sops runs can reuse a valid cached STS token instead of assuming the role each time.
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
- 35/100