-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Support modifying the association of a subnet with a network ACL #12364
Comments
This functionality has been released in v4.0.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! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
In case you have some additional ACLs (which isn't set as the default ACL) and you create a new subnet, you have no possibility to define which ACL should be used. It will use the default ACL as standard.
Currently there is no way to modify the default ACL association of a subnet.
I think we could create an aws_subnet_network_acl_association resource to solve this problem.
Only parameters needed are subnet_id and network_acl_id.
We could get the current associated ACL with "DescribeNetworkAcls" API call filtering for the subnet id. To replace it with the new ACL id the API call "ReplaceNetworkAclAssociation" should be used.
New or Affected Resource(s)
Potential Terraform Configuration
References
aws_subnet_network_acl_association
#5466The text was updated successfully, but these errors were encountered: