Construct for IAM Access Analyzer
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 74
Description
The announcement of IAM Access Analyzer on the 2nd December sees the introduction of a capability that mathematically analyzes access control policies attached to resources (S3, IAM Role, Lambda, KMS etc ...) and determines which resources can be accessed publicly or from other accounts
### Use Case
This service provides a greater visibility into the aggregate impact of your access control strategy, making it easy to report and to automatically respond to findings unintended resource access
### Proposed Solution
Implement CloudFormation Resource and CDK Construct for https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-accessanalyzer-analyzer.html
### Other
### References
https://aws.amazon.com/iam/features/analyze-access/
https://aws.amazon.com/blogs/aws/identify-unintended-resource-access-with-aws-identity-and-access-management-iam-access-analyzer/
https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html
---
This is a :rocket: Feature Request
Contributor guide
Research direction
Start with the AWS CloudFormation AWS::AccessAnalyzer::Analyzer documentation and the linked IAM Access Analyzer references. Determine the resource properties and the CDK construct surface needed for an analyzer covering the stated access-analysis use case. Done means the CloudFormation resource and corresponding CDK construct are implemented and validated against the documented behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100