Security Group
Last updated
Last updated
In Hyper, a security group acts as a virtual firewall that controls the traffic for one or more containers. You add rules to each security group that allow traffic to or from its associated containers. When we decide whether to allow traffic to reach a container, we evaluate all the rules from all the security groups that are associated with the container:
if a container has no associated security group, it is accessible (within the network it resides, as well as the Internet)
if a container has associated security group(s) with no egress
rule, it cannot access the Internet
if a container has associated security group(s) with no ingress
rule, it is not accessible from other containers, nor the Internet
Security group works independently from port, e.g. You need to publish the container ports even if the associated security group allows the traffic.
Security group is defined in a yaml file. Please read for more details.
When you launch a container, you associate one or more security groups with the container.
You can update containers to add or remove security groups.
To remove a security group from a container:
You can modify the rules for a security group on the fly; the new rules are automatically applied to all containers that are associated with the security group.
Note: You cannot remove a security group which is in use by containers.