Groups
Groups
Sign in
Groups
Groups
Terraform
Conversations
About
Send feedback
Help
How to to specify Port Range in aws_network_acl rules
636 views
Skip to first unread message
Rajinder Singh
unread,
Oct 17, 2015, 4:55:20 PM
10/17/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Terraform
I am creating a network acl for my subnet.
I need to define an ingress rule for ephemeral ports.
This requires specifying a port range like this one:
49152-65535
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_ACLs.html#VPC_ACLs_Ephemeral_Ports
Documentation of aws_network_acl is here:
https://www.terraform.io/docs/providers/aws/r/network_acl.html
to_port only allows specifying an integer. How can I specify a port range.
Raj
Daniel Bethke
unread,
Oct 17, 2015, 6:02:19 PM
10/17/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Terraform
There should also be a from_port that you can use for the beginning of the range
i think it should look something like this:
ingress {
rule_no
= 140
from_port
=
49152
to_port
=
65535
action
= "allow"
protocol
= "6"
cidr_block
= "
0.0.0.0/0
"
}
knope
unread,
Oct 22, 2015, 4:13:32 PM
10/22/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Terraform
you are correct.
Reply all
Reply to author
Forward
0 new messages