-
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
Add support for aws_subnet_network_acl_association
#5466
Comments
Hey @gkrizek ! We're beholden to the public API / SDK, which I'm having difficulty finding this API call in, do you by chance know where I can find it? I'm looking here: |
@catsby, I think you are right! I don't see any API method for associating a subnet with a Network ACL. So I guess it's not possible. I just ran my terraform template without this feature and it worked on. I just have to use the default Network ACL that is created with the VPC instead of creating a new one. So I'm able to work around it, but it's strange AWS doesn't have an API for that. |
@catsby would |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
We are missing something similar to
AWS::EC2::SubnetNetworkAclAssociation
in CloudFormation. There currently isn't a way to associate subnets with network acls. I think we need to create aaws_subnet_network_acl_association
resource for this. Only parameters needed aresubnet_id
andnetwork_acl_id
.New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: