Virtual private endpoint gateways
IBM Cloud® Virtual Private Endpoint (VPE) gateways provide private connectivity to IBM® Db2® as a Service from your VPC network. Traffic between your VPC and the Db2 service traverses the IBM Cloud private backbone network and does not pass through the public internet.
Before you begin
Before creating a virtual private endpoint gateway for your Db2 instance, ensure that you have the following:
- A IBM Cloud account with the required IAM permissions for VPC Infrastructure Services.
- An existing Virtual Private Cloud (VPC) in the same region as your Db2 instance.
- At least one subnet in your VPC for binding a reserved IP address.
- A provisioned Db2 Performance plan instance with at least private endpoints enabled.
To verify that private endpoints are enabled on your Db2 instance:
- Open the Db2 console.
- Select Administration from the left side menu.
- Select the Access restriction tab.
- Ensure that Private endpoints is toggled on.
VPE gateway connectivity is supported for Db2 instances on the Performance plan only.
Creating a virtual private endpoint gateway
To create a virtual private endpoint gateway for your Db2 instance, complete the following steps:
Step 1: Navigate to Virtual private endpoint gateways
- Log in to the IBM Cloud console.
- Click the Navigation Menu icon.
- Click Infrastructure > Network > Virtual private endpoint gateways.
The Virtual private endpoint gateways for VPC page is displayed. From here, you can view any existing endpoint gateways or create a new one.
Step 2: Create a new endpoint gateway
- Click Create.
- Under Location, select the Geography and Region that matches your Db2 instance. For example, if your Db2 instance is in Dallas, select North America and Dallas (us-south).
- Under Details, configure the following:
- Name: Enter a unique name for your endpoint gateway using lowercase alphanumeric characters and hyphens only (for example,
db2-test-vpeg). - Resource group: Select the resource group for the endpoint gateway.
- Tags (optional): Add tags to help organize and identify your resources.
- Virtual private cloud: Select the VPC where you want to create the endpoint gateway.
- Name: Enter a unique name for your endpoint gateway using lowercase alphanumeric characters and hyphens only (for example,
The region of the endpoint gateway must match the region of your Db2 instance.
Step 3: Configure security groups and select your Db2 service
- Under Security groups, select at least one security group to control traffic at the networking level. You can select up to five security groups.
- Under Request connection to a service, select IBM Cloud service.
- From the Cloud service offerings dropdown, select Db2.
- From the Cloud service regions dropdown, select the region where your Db2 instance is deployed (for example, Dallas (us-south)).
- From the list of available endpoints, select your Db2 instance.
Step 4: Configure DNS and reserved IP settings
- Under Share DNS, select the DNS resolution binding mode. The default is Primary.
- Under Reserved IP, choose a reserving method. You can reserve and bind a private IP from a subnet now or select Select later to configure this after creation.
- Review the Summary panel on the right for estimated costs.
- Click Create virtual private endpoint gateway.
After creation, the status of your endpoint gateway changes from Updating to Stable once the gateway is ready.
After creating the endpoint gateway
After the endpoint gateway status is Stable, you can connect to your Db2 instance using the private endpoint. The private endpoint hostname for your instance is available from the Connections tab in the Db2 console under Administration.
If you selected Select later for the reserved IP during creation, you can bind a reserved IP address at any time from the endpoint gateway details page.