When sops using AssumsRole, then Cloudtrail Log remain like 'sops@<hostname>'
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Our team monitroing All cloudtrail log who assume role.
When encrypting using AWS KMS and IAM roles in Sops, Cloudtrail logs are left in the form of '/sops@'.
arn": "<assume-role-arn>/sops@username-MacBookPro.local,
It is thought that a function should be added so that this part can be selectively provided in a form other than sops@.
arn": "<assume-role-arn>/<usename in AWS Account>
For example, add a function to leave a user's account with the -u option.
sops -e -u <filename>
then cloudtrail log remain log like below.
arn": "<assume-role-arn>/<username>
arn": "<assume-role-arn>/test@test.com or arn": "<assume-role-arn>/test
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 identified in the issue. Start by tracing the AWS KMS and assumed-role handling, then inspect how command-line options are parsed. Clarify whether -u accepts a username, email, or another value, and define the expected CloudTrail identity before adding coverage for the selected cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cli, cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100