Skip to main content

Configure network access to the Kafka cluster

By default, in clusters with a public subnet, the connection is allowed for all IP addresses if a username and password are provided.

For a cluster in a private subnet, the connection is allowed from the cluster subnet and from subnets that are connected to the cluster subnet via a cloud router.

You can define a list of allowed IP addresses from which access to the cloud database cluster will be allowed.

You can also use security groups to restrict access to the cloud database cluster.

Any changes to network access settings are the customer's responsibility.

Define a list of allowed IP addresses

When restoring a cluster from a backup, the list of allowed IP addresses will not be saved — for the new cluster, the allowed IP addresses will need to be specified again.

  1. In the control panel, in the top menu, click Products and select Cloud Databases.
  2. Open the Active tab.
  3. Open the database cluster page → Settings tab.
  4. In the Network Access Management section, click the field Allowed addresses and subnet CIDRs.
  5. At the bottom of the drop-down list, enter the CIDR of the subnet or the IP address from which access to the cluster should be allowed. Only IPv4 addressing is supported.
  6. Click .
  7. Repeat steps 5 and 6 for all allowed IP addresses.
  8. Click Save. All IP addresses except those specified in the allowed list will be denied connection.

Security groups in a Managed Database cluster

A security group in a cloud database cluster is a set of rules for filtering inbound and outbound cluster traffic. For security groups to work, traffic filtering (port security) must be enabled in the network.

If filtering is enabled in the network, all ports in this network are assigned the default security group, which allows all traffic through the ports. You can assign a different security group when creating a cluster or in an existing cluster.

In addition to the security groups you select when creating a cluster, a service security group is automatically assigned to Managed Database cluster network ports. This group keeps the cluster running and cannot be changed or deleted. The service group appears only in the OpenStack CLI and Terraform.

Learn more about security groups in the Security groups section.

Assign a security group in an existing cluster

warning

After assigning the group, all active sessions that do not comply with the group's rules will be terminated.

  1. Make sure that traffic filtering (port security) is enabled in the cluster network. To do this, in the control panel, in the top menu, click Products → Cloud Servers → Network → the Private networks or Public networks tab. A network with filtering enabled is marked with .

    If filtering is disabled, to use security groups, create a new cluster in a new subnet or in a subnet with traffic filtering enabled.

  2. In the control panel, in the top menu, click Products and select Cloud Databases.

  3. Open the Active tab.

  4. Open the database cluster page → Settings tab.

  5. In the Security block, click Edit.

  6. Select the security group to be assigned to all ports in the cluster network.

  7. Click .