| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2023-01-14 |
watsonplatform,virtual private endpoints |
watson |
{{site.data.keyword.attribute-definition-list}}
{: #virtual-private-endpoints}
[IBM Cloud]{: tag-ibm-cloud}
{{site.data.keyword.cloud}} Virtual Private Endpoints (VPE) for VPC enables you to connect to supported {{site.data.keyword.cloud}} services from your VPC network by using the IP addresses of your choosing, allocated from a subnet within your VPC. See more details here. {: shortdesc}
This document applies to {{site.data.keyword.conversationshort}}, {{site.data.keyword.discoveryshort}}, {{site.data.keyword.speechtotextshort}}, and {{site.data.keyword.texttospeechshort}}. Virtual Private Endpoints (VPEs) are available for these services in the Dallas, Washington, Frankfurt, London, Sydney, and Tokyo locations. {: note}
{: #prereqs-virtual-endpoints}
-
Have a Virtual Private Cloud (VPC)
-
Have private endpoints enabled for your service instance
{: #instructions-virtual-endpoints}
-
Creation of the VPEG is confirmed when an IP address is set in the details view of the VPEG page in the UI, CLI output of the
endpoint-gatewaycommand, or API details call.
You can verify by running nslookup <endpoint> on the private service endpoint of the {{site.data.keyword.watson}} service from your VPC, for example:
# nslookup api.private.us-south.assistant.watson.cloud.ibm.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: api.private.us-south.assistant.watson.cloud.ibm.com
Address: 10.240.0.9 <---- your VPE IP address{: codeblock}
To make requests using the assigned IP address instead of just the private service endpoint as suggested here, you must do your own hostname resolution. For example:
curl -X POST "https://api.private.us-south.assistant.watson.cloud.ibm.com/v2/assistants" --connect ::10.240.0.9{: pre}
curl -X POST "https://api.private.us-south.assistant.watson.cloud.ibm.com/v2/assistants" --resolve api.private.us-south.assistant.watson.cloud.ibm.com:443:10.240.0.9{: pre}
{: #additional-links-virtual-endpoints}