--- title: "Databases & Analytics - Configure your private network" description: "Learn how to connect a Public Cloud Instance, hosted in a data center, to a Cloud Database or Analytics service, hosted in another data center, like this:" url: https://docs.us.ovhcloud.com/en/public-cloud/databases/configure-private-network lang: en --- > For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt. # Databases & Analytics - Configure your private network **Learn how to connect a Public Cloud Instance, hosted in a data center, to a Cloud Database or Analytics service, hosted in another data center, like this:** The OVHcloud vRack is a private network solution that enables our customers to route traffic between OVHcloud dedicated servers as well as other OVHcloud services, such as Cloud Databases or Analytics services. The vRack also allows you to add Public Cloud instances to your private network to create an infrastructure of physical and virtual resources. For example, vRack can be configured for [Bare Metal servers](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md) and [Public Cloud](https://docs.us.ovhcloud.com/en/public-cloud/network-services/configure-vrack.md).   ## Requirements - Access to the [OVHcloud Control Panel](https://manager.us.ovhcloud.com/) - A [Public Cloud project](https://us.ovhcloud.com/public-cloud/) in your OVHcloud account   ## Considerations Here are some considerations to take into account when using a private network: - Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g., you won’t be able to delete the network if you didn’t stop the Cloud Databases or Analytics services first. - When connecting from an outside subnet, the OpenStack IP gateway must be enabled in the subnet used for the service. The customer is responsible for any other custom network setup. - Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.   ## Instructions ### Step 1 - Creating a virtual network The first step is to create the virtual network that will be used in your vRack. To proceed, consult this [guide](https://docs.us.ovhcloud.com/en/public-cloud/network-services/configure-vrack.md).   ### Step 2 - Creating a service connected to the private network Follow this [guide](https://docs.us.ovhcloud.com/en/public-cloud/databases/getting-started.md) to create a new Cloud Database or Analytics service, **while taking note of the information in the boxes below**. **Note:** Choose the plan that best fits your needs. The use of private networking with services is available with all plans. **Note:** - Select **Private** from the Network Type list, then choose **your private network**. - From the Subnetwork list, select the **10.0.0.0/16 - YYY**. _The YYY value is the name of the data center you chose._ - Then click `Next`.   ### Step 3 - Configure your instance to accept incoming connections Follow the _Configure your \[\_\_\_] instance to accept incoming connections_ guide of your selected engine type (available [here](https://docs.us.ovhcloud.com/en/public-cloud/databases/getting-started.md)) to configure your service after installation, **while taking note of the information in the boxes below**. **Note:** In the **IPs** panel, authorize the whole private network, as defined in previous steps, and click `+`. The service is now connected to the virtual network, we can use it from any component that is connected to the same vRack.   ### Step 4 - Adding your service to the vRack #### Public Cloud instances Follow this [guide](https://docs.us.ovhcloud.com/en/public-cloud/compute/getting-started.md) to create a new Public Cloud Instance, **while taking note of the information in the boxes below**. **Note:** For this step, select **your private network**, then click `Next`. **Note:** If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](https://docs.us.ovhcloud.com/en/public-cloud/network-services/configure-vrack.md).   #### Dedicated servers You can add your Dedicated server to vRack via the **Network** menu or through your server's **Network Interfaces** tab. See both methods in [this guide](https://docs.us.ovhcloud.com/en/bare-metal-cloud/dedicated-servers/vrack-configuring-on-dedicated-server.md#step-2-adding-your-servers-to-the-vrack).   ### Step 5 - Example of verification with Databases for PostgreSQL Connect to the instance and verify that you can reach your database by pinging the hostname: **Note:** The example below was [connected with Python](https://docs.us.ovhcloud.com/en/public-cloud/databases/postgresql-connect-python.md). You can also connect with [CLI](https://docs.us.ovhcloud.com/en/public-cloud/databases/postgresql-connect-cli.md), [PHP](https://docs.us.ovhcloud.com/en/public-cloud/databases/postgresql-connect-php.md), or [pgAdmin](https://docs.us.ovhcloud.com/en/public-cloud/databases/postgresql-connect-pgadmin.md). ``` ping postgresql-123abc45-123abc456.database.cloud.ovh.us # Expected Response PING postgresql-123abc45-123abc456.database.cloud.ovh.us (10.6.0.11) 56(84) bytes of data. 64 bytes from 10.6.0.11 (10.6.0.11): icmp_seq=1 ttl=64 time=69.5 ms 64 bytes from 10.6.0.11 (10.6.0.11): icmp_seq=2 ttl=64 time=63.4 ms 64 bytes from 10.6.0.11 (10.6.0.11): icmp_seq=3 ttl=64 time=63.1 ms 64 bytes from 10.6.0.11 (10.6.0.11): icmp_seq=4 ttl=64 time=63.1 ms ^C --- postgresql-123abc45-123abc456.database.cloud.ovh.us ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 63.080/64.801/69.537/2.737 ms ```   ## Go further Browse all the [Databases guides](https://docs.us.ovhcloud.com/en/public-cloud/databases/landing-page-databases.md). Browse the rest of the [OVHcloud US documentation](https://docs.us.ovhcloud.com/en/index.md) for guides on our other products and services. Learn more about [Managed Databases](https://us.ovhcloud.com/public-cloud/databases/) on the OVHcloud US website.