Skip to content

Commit bc2b19f

Browse files
committed
Clarification of Network ACL rules and Security group rules
1 parent 499f3a9 commit bc2b19f

File tree

2 files changed

+7
-0
lines changed

2 files changed

+7
-0
lines changed

source/adminguide/networking/security_groups.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,11 @@ Adding Ingress and Egress Rules to a Security Group
216216
#. Click Add.
217217

218218

219+
.. note::
220+
- If there is no Egress rule in a Security Group, all the outgoing traffic will be allowed
221+
- If there are Egress rules in a Security Group, only the outgoing traffic which match a Egress rule will be allowed
222+
- Only the incoming traffic which match a Ingress rule will be allowed
223+
219224
.. |httpaccess.png| image:: /_static/images/http-access.png
220225
:alt: allows inbound HTTP access from anywhere.
221226

source/adminguide/networking/virtual_private_cloud_config.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -355,6 +355,8 @@ Afterwards traffic can be white- or blacklisted.
355355
- ACL rules for ingress and egress are not correlating. For example a
356356
egress "deny all" won't affect traffic in response to an allowed ingress
357357
connection
358+
- The incoming traffic which does not match any ACL rules will be denied
359+
- The outgoing traffic which does not match any ACL rules will be allowed
358360

359361

360362
Creating ACLs

0 commit comments

Comments
 (0)