Lock down IAM security policies for product role secrets
Open
Nobody has claimed this yet.
aws
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
I think it's worth locking down the policies long term. Looks better in any security reviews and discussions with customers. The Okta Auth secret does this:
resources=[
f"arn:aws:secretsmanager:*:{account_id}:secret:okta-oidc-client-creds-*",
f"arn:aws:secretsmanager:*:{account_id}:secret:okta-oidc-client-creds.*.posit.team",
f"arn:aws:secretsmanager:*:{account_id}:secret:okta-oidc-client-creds.*.posit.team*",
],
Originally posted by @timtalbot in https://github.com/rstudio/ptd/pull/728#pullrequestreview-1928823569
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 file or test is named. Start by locating the IAM policy definitions for the product role and compare their Secrets Manager resource patterns with the Okta Auth example in this issue. Confirm which product-role secrets should be covered; done means the policies restrict access to those intended secret resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100