getsops / getsops/sops

Support AWS assume_role external id

Open
#1,095 1 comment 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
23.1k
Forks
1.1k
Avg merge
1d 11h
Merged PRs (30d)
9

Description

It would be cool if we could assume role with external id set. Something like this:

  - path_regex: secrets/environments/production/secrets.yaml
    kms: 'arn:aws:kms:us-east-1:666666666:key/xxxx-x-xxxxx+arn:aws:iam:us-east-1:666666666:role/kms_role'
    external_id: 'some_secret_external_id'

or

creation_rules:
  - kms: arn:aws:kms:us-east-1:666666666:key/xxxx-x-xxxxx+arn:aws:iam:us-east-1:666666666:role/kms_role+some_secret_external_id

What do you think?

Contributor guide

Open the contributing guide

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.

Research direction

Start by tracing how SOPS parses creation_rules and performs AWS role assumption for KMS. Check the existing AWS-related tests and configuration handling; done means an external ID can be configured for the role and is used during assumption without breaking existing KMS configuration formats.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.