-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
r/aws_config_organization_custom_policy_rule: New resource #28201
r/aws_config_organization_custom_policy_rule: New resource #28201
Conversation
Community NoteVoting for Prioritization
For Submitters
|
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.
Looks good to me!
Hello guys, when we could expect this PR to be merged ? My organization is looking for this exact solution at the moment. Thank you in advance. |
@gpetrovgeorgi You've encouraged me to get the tests passing again :) |
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.
LGTM 🚀.
@georgealton Thanks for the contribution 🎉 👏. |
This functionality has been released in v4.65.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Looks like the changelog accidentally referred to PR #21373 rather than this PR :) |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This adds a new resource
aws_config_organization_custom_policy_rule
AWS Config Rules added the capability to use a CloudFormation Guard Policy as a declarative way of performing assertions against resource configuration, without having to manage a Lambda Function.
The Provider gained the capability to manage Account Level CFN Guard Policy backed Rules, but not learn this for Organization Config Rules.
This PR adds the Organization Rule Resource, allowing a team to easily apply a policy to an entire organization, without having to manage and deploy Lambda functions to many accounts.
This feature is really useful for central enabling teams looking to validate best practice compliance in a multi AWS account, high autonomy, organization.
Relations
Closes #27987
Closes #26989
References
API Docs: https://docs.aws.amazon.com/config/latest/APIReference/API_PutOrganizationConfigRule.html
Related Config Rule Resource: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/config_config_rule#custom-policy-details
Output from Acceptance Testing
It was tricky to get all the Acceptance tests to pass together, there is some eventual consistency between organizations and config that sometimes in resulted in AWS Config reporting that the account wasn't a member of an Organization. This might be addressable with more thought on #11582