-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
AWS --- aws_network_acl -- subnet_id #1735
Comments
Hey @rainmanh – Have you been able to do this elsewhere, with AWS Console or otherwise? |
(closing for now, as this is working as documented and according to the AWS API) |
Hi http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_ACLs.html Associating a Subnet with a Network ACL To apply the rules of a network ACL to a particular subnet, you must associate the subnet with the network ACL. You can associate a network ACL with multiple subnets; however, a subnet can be associated with only one network ACL. Any subnet not associated with a particular ACL is associated with the default network ACL by default. |
Hello – I just merged #1931 which provides support for multiple subnet ids, and will go out in the next release. |
thanks very much guys!! |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi
using AWS as a privisioner and for the aws_network_acl resource I am trying to associated multiple subnet_id but it does not seem to work, I just get crashes.
subnet_id = ["${var.resource.1}","${var.resource.1}"]
It only seems to work for one:
subnet_id = "${var.resource.1}"
Maybe I am using the wrong syntax for it?
thanks!
The text was updated successfully, but these errors were encountered: