# Adding a new rule to a security group You do not need to restart a VM when adding or deleting [rules](../concepts/security-groups.md#security-groups-structure). The rules are applied to all the resources associated with a group at the same time. {% list tabs group=instructions %} - Management console {#console} To add a rule: 1. In the [management console](https://console.yandex.cloud), select the folder containing the [security group](../concepts/security-groups.md) you want to update. 1. Navigate to **Virtual Private Cloud**. 1. In the left-hand panel, select ![image](../../_assets/console-icons/shield.svg) **Security groups**. 1. Click ![image](../../_assets/console-icons/ellipsis.svg) in the row of the security group you need to add a rule to. Select **Edit**. 1. Under **Rules**, create traffic management rules: 1. Select the **Egress** or **Ingress** tab. 1. Click **Add**. 1. In the **Port range** field of the window that opens, specify a single port or a range of ports open for inbound or outbound traffic. 1. In the **Protocol** field, specify the appropriate protocol or leave `Any` to allow traffic transmission over any protocol. 1. In the **Destination name** or **Source** field, select the rule purpose: * `CIDR`: Rule will apply to the range of IP addresses. In the **CIDR blocks** field, specify the CIDRs and masks of subnets traffic will move to/from. To add multiple CIDRs, click **Add**. * `Security group`. Select one of the following: * `Current`: Rule will apply to the VMs from the current group. * `From list`: Rule will apply to the VMs from the selected group. Make sure that source and destination IP addresses used for traffic exchange are from [private ranges](../concepts/network.md#subnet). For more information, see [Concepts](../concepts/security-groups.md#groups). * `Load balancer healthchecks`: Rule that allows checking the health of resources from [Network Load Balancer](../../network-load-balancer/concepts/health-check.md) or [Application Load Balancer](../../application-load-balancer/concepts/backend-group.md#health-checks). 1. Click **Save**. 1. Click **Save** once again. - CLI {#cli} To add a rule to an existing [group](../concepts/security-groups.md): 1. Get the name or ID of the group to edit: ``` yc vpc security-groups list ``` Result: ``` +----------------------+---------------------------------+------------------------------------+----------------------+ | ID | NAME | DESCRIPTION | NETWORK-ID | +----------------------+---------------------------------+------------------------------------+----------------------+ | enp9bmjge93b******** | default-sg-enp509crtquf******** | Default security group for network | enp509crtquf******** | | enp9rs9u4h6j******** | sg-1 | | enp509crtquf******** | | enp9d8m73d1c******** | sg-2 | | enp509crtquf******** | +----------------------+---------------------------------+------------------------------------+----------------------+ ``` 1. Add a rule using the `update-rules` command and the `--add-rule` parameter: ``` yc vpc security-group update-rules --add-rule "direction=ingress,port=443,protocol=tcp,v4-cidrs=[10.0.0.0/24,10.10.0.0/24]" ``` Result: ``` done (12s) id: enp9rs9i4h9j******** folder_id: b1gau98l79li******** created_at: "2022-06-24T15:46:31Z" name: sg-1 network_id: enp559cr9q9f******** status: ACTIVE rules: - id: enp68o6cdi87******** direction: INGRESS ports: from_port: "443" to_port: "443" protocol_name: TCP protocol_number: "6" cidr_blocks: v4_cidr_blocks: - 10.0.0.0/24 - 10.10.0.0/24 ... ``` {% note info %} You can use `predefined=self_security_group` to apply the rule to the VMs inside the security group you are updating. For more information about the `Self` rule, see the [types of security group rules](../concepts/security-groups.md#rules-types). {% endnote %} To learn about the `--add-rule` parameter, run the `yc vpc security-group update-rules --help` command. - Terraform {#tf} If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform). To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../terraform/authentication.md) using the appropriate method. With [Terraform](https://www.terraform.io/), you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed. Terraform is distributed under the [Business Source License](https://github.com/hashicorp/terraform/blob/main/LICENSE). The [Yandex Cloud provider for Terraform](https://github.com/yandex-cloud/terraform-provider-yandex) is distributed under the [MPL-2.0](https://www.mozilla.org/en-US/MPL/2.0/) license. For more information about the provider resources, see the relevant documentation on the [Terraform](https://www.terraform.io/docs/providers/yandex/index.html) website or [its mirror](../../terraform/index.md). 1. Open the Terraform configuration file and add the `ingress` or `egress` section to the [security group](../concepts/security-groups.md) description: ```hcl ... resource "yandex_vpc_security_group" "test-sg" { name = "Test security group" description = "Description for security group" network_id = "${yandex_vpc_network.lab-net.id}" ingress { protocol = "TCP" description = "Rule description 1" v4_cidr_blocks = ["10.0.1.0/24", "10.0.2.0/24"] port = 8080 } egress { protocol = "ANY" description = "Rule description 2" v4_cidr_blocks = ["10.0.1.0/24", "10.0.2.0/24"] from_port = 8090 to_port = 8099 } egress { protocol = "UDP" description = "rule3 description" v4_cidr_blocks = ["10.0.1.0/24"] from_port = 8090 to_port = 8099 } } ... ``` For more information about `yandex_vpc_security_group` properties in Terraform, see [this provider guide](../../terraform/resources/vpc_security_group.md). 1. Check the configuration using this command: ``` terraform validate ``` If the configuration is valid, you will get this message: ``` Success! The configuration is valid. ``` 1. Run this command: ``` terraform plan ``` You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration. 1. Apply the configuration changes: ``` terraform apply ``` 1. Confirm the changes: type `yes` into the terminal and press **Enter**. You can check the security group update using the [management console](https://console.yandex.cloud) or this [CLI](../../cli/quickstart.md) command: ``` yc vpc security-group get ``` ### Adding a new rule using the yandex_vpc_security_group_rule resource {#add-rule-with-yandex-vpc-security-group-rule} You can also add a new rule to an existing security group using the `yandex_vpc_security_group_rule` resource. {% note warning %} Both methods provide the same result but they are incompatible: concurrent use of the `yandex_vpc_security_group_rule` and `yandex_vpc_security_group` resources will cause a configuration rule conflict. {% endnote %} 1. In the configuration file, describe the following parameters: * `security_group_binding`: Security group ID. * `direction`: Incoming or outgoing traffic. The possible values are `ingress` or `egress`. * `description`: Rule description. * `v4_cidr_blocks`: List of CIDRs and masks of subnets the traffic will come to or from. * `port`: Traffic port. * `from_port`: First port in the traffic port range. * `to_port`: Last port in the traffic port range. * `protocol`: Traffic transmission protocol. The possible values are `TCP`, `UDP`, `ICMP`, or `ANY`. ```hcl ... resource "yandex_vpc_security_group_rule" "rule1" { security_group_binding = direction = "ingress" description = "" v4_cidr_blocks = ["10.0.1.0/24", "10.0.2.0/24"] port = 8080 protocol = "TCP" } resource "yandex_vpc_security_group_rule" "rule2" { security_group_binding = yandex_vpc_security_group.group1.id direction = "egress" description = "rule2 description" v4_cidr_blocks = ["10.0.1.0/24"] from_port = 8090 to_port = 8099 protocol = "UDP" } ... ``` For more information about `yandex_vpc_security_group_rule` properties in Terraform, see [this provider guide](../../terraform/resources/vpc_security_group_rule.md). 1. Validate your configuration using this command: ``` terraform validate ``` If the configuration is valid, you will get this message: ``` Success! The configuration is valid. ``` 1. Run this command: ``` terraform plan ``` You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration. 1. Apply the configuration changes: ``` terraform apply ``` 1. Confirm the changes: type `yes` into the terminal and press **Enter**. You can check the security group update using the [management console](https://console.yandex.cloud) or this [CLI](../../cli/quickstart.md) command: ``` yc vpc security-group get ``` - API {#api} To add a rule, use the [updateRules](../api-ref/SecurityGroup/updateRules.md) REST API method for the [SecurityGroup](../api-ref/SecurityGroup/index.md) resource or the [SecurityGroupService/UpdateRules](../api-ref/grpc/SecurityGroup/updateRules.md) gRPC API call, and provide the following in the request: * ID of the [security group](../concepts/security-groups.md) you want to add rules to, in the `securityGroupId` parameter. To get the security group ID, use the [list](../api-ref/SecurityGroup/list.md) REST API method for the [SecurityGroup](../api-ref/SecurityGroup/index.md) resource or the [SecurityGroupService/List](../api-ref/grpc/SecurityGroup/list.md) gRPC API call and provide the folder ID in the `folderId` request parameter. To learn how to find out the folder ID, see [Getting the folder ID](../../resource-manager/operations/folder/get-id.md). * New security group rules, in the `additionRuleSpecs[]` array: * Traffic direction for which the rule is created, in the `additionRuleSpecs[].direction` parameter. The possible values are: * `ingress`: Incoming traffic. * `egress`: Outgoing traffic. * Name of the traffic transmission protocol, in the `additionRuleSpecs[].protocolName` parameter. The possible values are `tcp`, `udp`, `icmp`, `esp`, `ah`, or `any`. * List of CIDRs and masks of subnets the traffic will come to or from, in the `additionRuleSpecs[].cidrBlocks.v4CidrBlocks[]` parameter. If you set the rule for the traffic to a security group, provide the security group ID in the `additionRuleSpecs[].securityGroupId` parameter instead. * First port in the traffic port range, in the `additionRuleSpecs[].ports.fromPort` parameter. The values range from `0` to `65535`. * Last port in the traffic port range, in the `additionRuleSpecs[].ports.toPort` parameter. The values range from `0` to `65535`. {% endlist %}