-
Notifications
You must be signed in to change notification settings - Fork 290
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
DRAFT - Allow creation of Wafv2 ACL resources through CloudFormation #7162
Conversation
…ermissions that allow only the creation of wafv2:acl resources via an aws_cloudformation_stack.
Please check the plan carefully before deploying these changes.
|
|
Change applied to sprinkler for testing. |
…owing the stack creation with the required resource type.
Please check the plan carefully before deploying these changes.
|
|
Please check the plan carefully before deploying these changes.
|
|
Please check the plan carefully before deploying these changes.
|
|
|
Please check the plan carefully before deploying these changes.
|
|
Please check the plan carefully before deploying these changes.
|
|
Please check the plan carefully before deploying these changes.
|
|
New solution offered by AWS so testing that first before any new PR. |
Note - this is pending advice from AWS on issues arising from this proposed change.
Amends aws_iam_policy_document "member-access" and adds permissions that allow only the creation of wafv2:acl resources via an aws_cloudformation_stack. Note that the permissions are limited only to stack-level operations and does not include those actions for stacksets or the creation/exec of changesets.
A reference to the issue / Description of it
See issue 6991 - #6991
How does this PR fix the problem?
This change has been requested by the LAA Ops team due to limitations with terraform implementing wafv2:acl rules nested beyond 3 levels. The identified solution is to create the acl via an aws_cloudformation_stack resources. The added statement has been written to only allow the creation of resources of type AWS:WAFv2:ACL via cloudformation so as to avoid the potential for this approach to be used more generally.
How has this been tested?
Please describe the tests that you ran and provide instructions to reproduce.
This change will be tested in sprinkler first where I will attempt to create both a wafv2:acl and other types of resource. If the tests are successful, the acl will be created via a cloudformation stack but not others.
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
As this is a supplemental change it should not adversely impact existing resources.
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
{Please write here}