Creating a PostgreSQL Cluster in a Custom VPC/VNet
This support documentation page will walk you through the process of provisioning an Instaclustr Managed PostgreSQL cluster or a data centre in an existing VPC/VNet that you manage. This is only possible for those customers who are running an Instaclustr managed cluster in their own cloud account.
Potential Use Cases
Instaclustr has identified the following use cases for this feature:
- Customers with custom/complex network configuration setup. For example, AWS Direct Connect or VPC Transit Gateways networking can all be set up once for a VPC and then that VPC reused for multiple clusters.
- Customers looking to minimise Cloud provider’s network costs. For some use cases, cross VPC/VNet traffic can be a significant portion of overall infrastructure costs.
- Customers with a fully automated CI/CD implementation for their application that would like to provision and manage clusters running on the Instaclustr Managed platform. Setting up the VPC/VNet and peering once and then recreating clusters as necessary will make it easier to implement a fully automated CI/CD.
Enable the Feature for Your Account
Before using this feature you must have it enabled on your account.
Contact Instaclustr Support to enable the ability to create a Custom VPC/VNet cluster or data centre.
Console – Create a New Cluster or Add a Data Centre
Once the feature is enabled, you need to supply the following fields when you create a cluster or add an additional cluster data centre:
Data Centre Options
| Provider Account | Your previously setup custom AWS/GCP/AZURE_AZ account.* |
| Data Centre | The region the VPC/VNet resides in.* |
| Custom Name | The name you wish to give your data centre. |
| Cluster Network | An IPv4 CIDR block for the private network Instaclustr will use to set up the cluster.** |
| Custom Virtual Network ID | The ID of the custom VPC/VNet.* |
* If the provided Account, VPC/VNet and Region do not match, provisioning of the cluster or data centre will fail and you will need to contact Instaclustr Support.
* AWS Custom VPC Id Format:
1 | vpc-06b9b4c424cd45a0e |
* Azure Custom VNet Id Format:
1 | /subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Network/virtualNetworks/{virtual-network-name} |
** The provided VPC must have this address space available; providing an incorrect CIDR or a Data Centre Network that is already taken will cause provisioning to fail and you will need to contact Instaclustr Support.
** For Azure Custom VNet, when setting CLUSTER NETWORK, you should use a CIDR that doesn’t overlap any existing address spaces in your VNet.
Provisioning API – Create a New Cluster
For more detailed information about the Provisioning API, see our support documentation.
AWS Example
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 | { "dataCentres": [ { "clientToClusterEncryption": true, "cloudProvider": "AWS_VPC", "intraDataCentreReplication": [ { "replicationMode": "SYNCHRONOUS" } ], "providerAccountName": "<provider-account-name>", "awsSettings": [ { "customVirtualNetworkId": "<custom-vnet-id>" } ], "name": "dc_1", "network": "10.1.0.0/16", "nodeSize": "PGS-DEV-t4g.small-5", "numberOfNodes": 2, "region": "US_EAST_1" } ], "extensions": [ { "extensionEnabled": false, "extensionName": "PgVector" } ], "name": "test_apiv2_postgresql_create", "postgresqlVersion": "16.0.0", "privateNetworkCluster": false, "slaTier": "NON_PRODUCTION", "synchronousModeStrict": false } |
- providerAccountName, customVirtualNetworkId & dataCentre
The values for these fields must align with an existing VPC; if not, provisioning of the cluster or data centre will fail and you will need to contact Instaclustr Support. - clusterNetwork
The desired custom VPC must have this address space available; providing an incorrect CIDR or an address space that is already occupied will cause provisioning to fail and you will need to contact Instaclustr Support.
Azure Example
The example request below will create a 2 node PostgreSQL 16.0.0 cluster within a Custom Azure VNet.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | { "dataCentres": [ { "clientToClusterEncryption": true, "cloudProvider": "AZURE_AZ", "intraDataCentreReplication": [ { "replicationMode": "SYNCHRONOUS" } ], "name": "AZURE_AZ_EAST_US_2", "network": "10.1.0.0/16", "nodeSize": "PGS-DEV-Standard_DS1_v2-30-an", "numberOfNodes": 2, "region": "EAST_US_2", "providerAccountName": "<provider-account-name>", "azureSettings": [ { "customVirtualNetworkId": "<custom-vnet-id>", "resourceGroup": "<resource-group-name> (Optional, depends on whether your provider account is Subscription level or Resource Group level)" } ] } ], "name": "test-postgresql-cluster", "postgresqlVersion": "16.0.0", "privateNetworkCluster": false, "slaTier": "NON_PRODUCTION", "synchronousModeStrict": false } |
Take care to set the following fields correctly:
- resourceGroup, customVirtualNetworkId & dataCentre
The values for these fields must align with an existing VNet; if not, provisioning of the cluster or data centre will fail and you will need to contact Instaclustr Support. - clusterNetwork
The desired custom VNet must have this address space available; providing an incorrect CIDR or an address space that is already occupied will cause provisioning to fail and you will need to contact Instaclustr Support.
What Gets Created?
This information is used by our provisioning system to set up your cluster data centre.
The following objects will get created in the Custom VPC/VNet:
AWS
- An internet gateway
- Subnets for the nodes
- Route table to route traffic to these subnets
- Security groups to control access to the nodes
- EC2 Instances – 1 per node
- Public IP address – 1 per node (unless private network cluster)
- EBS disk – as required by node size
Private network clusters have two additional components:
- An EC2 instance acting as an SSH gateway
- A NAT gateway instead of an internet gateway
Azure
- An address space with the CIDR of the CLUSTER NETWORK added to the VNet
- A Subnet for the date centre using the address space
- Security groups to control access to the nodes
- Virtual machines – 1 per node
- Public IP address – 1 per node (unless private network cluster)
- Data disk – 1 per node
All of these objects are created by our system and their unique id is stored in our internal database.
Tagging Objects
Instaclustr tags each object it creates. Custom tags may also be added to your account which will also be applied to all objects created.
In this way, customers can easily identify which objects make up the cluster data centre. For more information on tags, refer to our support article Adding Tags to Clusters.
Deleting Objects
When deprovisioning a cluster, Instaclustr only removes objects that we have created and stored in our database. We will not delete the custom VPC/VNet you have provided in any circumstances.
By Instaclustr Support