Documentation: explain the role of to_port in a security group rule when protocol is "icmp" (#8093)
This commit is contained in:
parent
3fc119923e
commit
8bba3d4e6e
|
@ -92,7 +92,7 @@ The `ingress` block supports:
|
|||
EC2-Classic, or Group IDs if using a VPC.
|
||||
* `self` - (Optional) If true, the security group itself will be added as
|
||||
a source to this ingress rule.
|
||||
* `to_port` - (Required) The end range port.
|
||||
* `to_port` - (Required) The end range port (or ICMP code if protocol is "icmp").
|
||||
|
||||
The `egress` block supports:
|
||||
|
||||
|
@ -105,7 +105,7 @@ The `egress` block supports:
|
|||
EC2-Classic, or Group IDs if using a VPC.
|
||||
* `self` - (Optional) If true, the security group itself will be added as
|
||||
a source to this egress rule.
|
||||
* `to_port` - (Required) The end range port.
|
||||
* `to_port` - (Required) The end range port (or ICMP code if protocol is "icmp").
|
||||
|
||||
~> **NOTE on Egress rules:** By default, AWS creates an `ALLOW ALL` egress rule when creating a
|
||||
new Security Group inside of a VPC. When creating a new Security
|
||||
|
@ -160,4 +160,4 @@ Security Groups can be imported using the `security group id`, e.g.
|
|||
|
||||
```
|
||||
$ terraform import aws_security_group.elb_sg sg-903004f8
|
||||
```
|
||||
```
|
||||
|
|
|
@ -51,7 +51,7 @@ Only valid with `egress`.
|
|||
depending on the `type`. Cannot be specified with `cidr_blocks`.
|
||||
* `self` - (Optional) If true, the security group itself will be added as
|
||||
a source to this ingress rule.
|
||||
* `to_port` - (Required) The end range port.
|
||||
* `to_port` - (Required) The end range port (or ICMP code if protocol is "icmp").
|
||||
|
||||
## Usage with prefix list IDs
|
||||
|
||||
|
|
Loading…
Reference in New Issue