There are SecretsManager secret resources without a KMS ID supplied, leading to the default Customer Master Key being used
Open
Nobody has claimed this yet.
funder/otffoss2025
- Dominant language
- HCL
- Stars
- 4
- Forks
- 15
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 4
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
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
The issue body names no files, tests, or entry points. Start by searching the repository for SecretsManager secret resources and their KMS settings, then identify which resources lack an explicit key ID. Done means the affected resources use the intended KMS ID rather than the default customer master key, with relevant validation or deployment checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100