Skip to main content

Configure network access to a PostgreSQL cluster

Last update:

By default, in clusters with a public subnet, the connection is allowed for all IP addresses if a login 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 Managed Database cluster will be allowed.

To restrict access to the Managed Database cluster, you can also use security groups.

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 specify the allowed IP addresses again.

  1. In the Dashboard, on 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 block, click the Allowed IP addresses and CIDR subnets 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. All IP addresses, except for those specified in the allow list, will be blocked from connecting.

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 cluster traffic. For security groups to work, traffic filtering (port security) must be enabled in the network.

If filtering is enabled in a network, a default security group is assigned to all ports in that network, 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 you create the cluster, a service security group is automatically assigned to the 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.

More about security groups in the Security groups section.

Assign a security group in an existing cluster

warning

After the group is assigned, all active sessions that do not comply with the group rules will be terminated.

  1. Ensure that traffic filtering (port security) is enabled in the cluster network. To do this, in the Dashboard on the top menu, click Products → Cloud Servers → Network → 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 logical replication or a logical dump.

  2. In the Dashboard, on 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 block, click Edit.

  6. Select the security group you want to assign to all ports in the cluster network.

  7. Click .