-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(cdk greenfield support): Changes to support greenfield account restrictions present in higher environments #700
Conversation
… greenfield accounts
also note, the clamscan dependency at the top level can probably be removed. thats unrelated but i noticed it |
Coverage Report
File Coverage
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not an AWS powerhouse, but LGTM
Code Climate has analyzed commit c89a0d8 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 0.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 52.4% (-0.1% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ship it
|
||
public visit(node: IConstruct): void { | ||
if (node instanceof iam.Role && isCfnRole(node.node.defaultChild)) { | ||
node.node.defaultChild?.addPropertyOverride("Path", this.iamPath); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed this ?
. The other ones don't have it so I'm assuming you forgot this one?
🎉 This PR is included in version 1.5.0-val.69 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Purpose
In higher environments, iam path and permissions boundary is enforced on our users and service roles. This required modifying the cdk tool kit bootstrapping process, as well as adding config to our application.
Linked Issues to Close
None
Approach
The CDK is bootstrapped with a template that accounts for iam path and permissions boundary. The roles generated are then passed in the synthesizer config. Finally, two cdk aspects ensure all iam objects built by our application have the path and permissionsboundary set.
Assorted Notes/Considerations/Learning
A procedure on bootstrapping cdk is warranted, and will come along a bit later.