aws / aws/aws-cdk

(cli): Integrate with IAM Access Analyzer policy validation

Open
#13,649 2 comments 1 reaction 0 assignees View on GitHub
@aws-cdk/aws-accessanalyzer @aws-cdk/aws-iam closed-for-staleness effort/large feature-request p2 package/tools
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
2d 3h
Merged PRs (30d)
83

Description

Integrate IAM Access Analyzer policy validation with the CLI, either with a special command or during `deploy`.

It could also be used as a new "linting" tool in the repo to ensure that IAM policies created by AWS CDK constructs comply with best practices.

See https://aws.amazon.com/blogs/aws/iam-access-analyzer-update-policy-validation/
See https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html

### Use Case

* Warn users if their CDK code generates "bad" IAM policies
* Ensure AWS CDK constructs deliver IAM policies that are compliant with best practices

### Proposed Solution

To be discussed 😄

* [x] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change

---

This is a :rocket: Feature Request

Contributor guide

Open the contributing guide

Research direction

Start with the IAM Access Analyzer policy validation documentation and the CLI's deploy flow, since the issue proposes either a dedicated command or deploy-time validation. Define the integration point, warning or failure behavior, and repository linting scope before implementation; done means CDK-generated IAM policies are checked against the selected validation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cli, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.