You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The inbound and outbound access rules to apply to the Firewall.
20954
20958
20955
20959
A Firewall may have up to 25 rules across its inbound and outbound rulesets.
20960
+
20961
+
Multiple rules are applied in order. If two rules conflict, the first rule takes precedence. For example, if the first rule accepts inbound traffic from an address, and the second rule drops inbound traffic the same address, the first rule applies and inbound traffic from that address is accepted.
20956
20962
properties:
20957
20963
inbound:
20958
20964
type: array
@@ -21009,41 +21015,49 @@ components:
21009
21015
- ICMP
21010
21016
- IPENCAP
21011
21017
description: >
21012
-
The type of network traffic to allow.
21018
+
The type of network traffic affected by this rule.
21013
21019
example: TCP
21014
21020
ports:
21015
21021
type: string
21022
+
nullable: true
21016
21023
description: |
21017
-
A string representing the port or ports on which traffic will be allowed:
21024
+
A string representing the port or ports affected by this rule:
21018
21025
21019
21026
- The string may be a single port, a range of ports, or a comma-separated list of single ports and port ranges. A space is permitted following each comma.
21020
21027
- A range of ports is inclusive of the start and end values for the range. The end value of the range must be greater than the start value.
21021
21028
- Ports must be within 1 and 65535, and may not contain any leading zeroes. For example, port "080" is not allowed.
21022
-
- Ports may not be specified if a rule's protocol is `ICMP` or `IPENCAP`.
21023
-
- At least one port must be specified if a rule's protocol is `TCP` or `UDP`.
21024
21029
- The ports string can have up to 15 *pieces*, where a single port is treated as one piece, and a port range is treated as two pieces. For example, the string "22-24, 80, 443" has four pieces.
21030
+
- If no ports are configured, all ports are affected.
21031
+
- Only allowed for the TCP and UDP protocols. Ports are not allowed for the ICMP and IPENCAP protocols.
21025
21032
example: '22-24, 80, 443'
21026
21033
addresses:
21027
21034
type: object
21028
-
description: >
21029
-
Allowed IPv4 or IPv6 addresses. A Rule can have up to 255 addresses
21030
-
or networks listed across its IPv4 and IPv6 arrays. A network and a single IP
21031
-
are treated as equivalent when accounting for this limit.
21035
+
description: |
21036
+
The IPv4 and/or IPv6 addresses affected by this rule. A Rule can have up to 255 total addresses or networks listed across its IPv4 and IPv6 arrays. A network and a single IP are treated as equivalent when accounting for this limit.
21037
+
21038
+
Must contain `ipv4`, `ipv6`, or both.
21032
21039
properties:
21033
21040
ipv4:
21034
-
description: A list of IPv4 addresses or networks. Must be in IP/mask format.
21041
+
description: |
21042
+
A list of IPv4 addresses or networks. Addresses must be in IP/mask format. Must not be an empty list.
21043
+
21044
+
If "0.0.0.0/0" is included in this list, all IPv4 addresses are affected by this rule.
21035
21045
type: array
21036
21046
items:
21037
21047
type: string
21038
21048
example:
21039
21049
- 192.0.2.0/24
21050
+
- 198.51.100.2/32
21040
21051
ipv6:
21041
-
description: A list of IPv6 addresses or networks. Must be in IP/mask format.
21052
+
description: |
21053
+
A list of IPv6 addresses or networks. Addresses must be in IP/mask format. Must not be an empty list.
21054
+
21055
+
If "::/0" is included in this list, all IPv6 addresses are affected by this rule.
0 commit comments