Skip to content
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

Closed
rainmanh opened this issue Apr 29, 2015 · 6 comments
Closed

AWS --- aws_network_acl -- subnet_id #1735

rainmanh opened this issue Apr 29, 2015 · 6 comments

Comments

@rainmanh
Copy link

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!

@catsby
Copy link
Contributor

catsby commented Apr 29, 2015

Hey @rainmanh – subnet_id is a single entity here; it doesn't accept an array/multiple subnets:

Have you been able to do this elsewhere, with AWS Console or otherwise?

@catsby
Copy link
Contributor

catsby commented Apr 29, 2015

(closing for now, as this is working as documented and according to the AWS API)

@catsby catsby closed this as completed Apr 29, 2015
@ghost
Copy link

ghost commented Apr 29, 2015

Hi
yes, you can do that with the console. you can have several subnet associations per ACL.

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.

@catsby
Copy link
Contributor

catsby commented May 15, 2015

Hello – I just merged #1931 which provides support for multiple subnet ids, and will go out in the next release.

@rainmanh
Copy link
Author

thanks very much guys!!

@ghost
Copy link

ghost commented May 2, 2020

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.

@ghost ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants