Skip to main content

Configure network access to a PostgreSQL for 1C cluster

By default, in clusters with a public subnet, connection is allowed for all addresses, provided you have a username and password.

For a cluster in a private subnet, 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 managed database cluster will be allowed.

You can also use security groups to restrict access to a managed database cluster.

Any changes to network access settings are the client'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, you will need to re-enter the allowed IP addresses.

  1. In the control panel, in the top menu, click Products and select Managed Databases.
  2. Open the Active tab.
  3. Open the database cluster page → Settings tab.
  4. In the Network access management section, click the Allowed addresses and subnet CIDRs field.
  5. At the bottom of the drop-down list, enter the subnet CIDR 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. Connections from all IP addresses except those specified in the allowed list will be denied.

Security groups in a Managed Database cluster

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

If filtering is enabled on 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 the Managed Database cluster network ports. This group is required for the cluster to function and cannot be changed or deleted. The service group is only visible in the OpenStack CLI and Terraform.

Learn more about security groups in the Security Groups section.

Assign a security group to an existing cluster

warning

After assigning a 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 and migrate the data using a logical dump.

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

  3. Open the Active tab.

  4. Open the database cluster page → Settings tab.

  5. In the Security section, click Edit.

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

  7. Click .