IBM Cloud Docs
Using virtual private endpoints for VPC to privately connect to Activity Tracker Event Routing

Using virtual private endpoints for VPC to privately connect to Activity Tracker Event Routing

IBM Cloud® Virtual Private Endpoints (VPE) for VPC enables you to connect to Activity Tracker Event Routing from your VPC network by using the IP addresses of your choosing, allocated from a subnet within your VPC.

VPEs are virtual IP interfaces that are bound to an endpoint gateway created on a per service, or service instance, basis (depending on the service operation model). The endpoint gateway is a virtualized function that scales horizontally, is redundant and highly available, and spans all availability zones of your VPC. Endpoint gateways enable communications from virtual server instances within your VPC and the IBM Cloud® service on the private backbone. VPE for VPC gives you the experience of controlling all the private addressing within your cloud. For more information, see About virtual private endpoint gateways.

Before you begin

Before you target a virtual private endpoint for Activity Tracker Event Routing you must complete the following tasks.

Setting up a VPE for Activity Tracker Event Routing

When you create a VPE gateway by using the CLI or API, you must specify the Cloud Resource Name (CRN) of the region in which you want connect to Activity Tracker Event Routing. Review the following table for the available regions and CRNs to use to create your VPE gateway.

Region availability and Cloud Resource Names for connecting Activity Tracker Event Routing over IBM Cloud private networks
Region Cloud Resource Name (CRN)
au-syd crn:v1:bluemix:public:atracker:au-syd:::endpoint:private.au-syd.atracker.cloud.ibm.com
br-sao crn:v1:bluemix:public:atracker:br-sao:::endpoint:private.br-sao.atracker.cloud.ibm.com
ca-tor crn:v1:bluemix:public:atracker:ca-tor:::endpoint:private.ca-tor.atracker.cloud.ibm.com
eu-de crn:v1:bluemix:public:atracker:eu-de:::endpoint:private.eu-de.atracker.cloud.ibm.com
eu-es crn:v1:bluemix:public:atracker:eu-es:::endpoint:private.eu-es.atracker.cloud.ibm.com
eu-gb crn:v1:bluemix:public:atracker:eu-gb:::endpoint:private.eu-gb.atracker.cloud.ibm.com
jp-osa crn:v1:bluemix:public:atracker:jp-osa:::endpoint:private.jp-osa.atracker.cloud.ibm.com
jp-tok crn:v1:bluemix:public:atracker:jp-tok:::endpoint:private.jp-tok.atracker.cloud.ibm.com
us-east crn:v1:bluemix:public:atracker:us-east:::endpoint:private.us-east.atracker.cloud.ibm.com
us-south crn:v1:bluemix:public:atracker:us-south:::endpoint:private.us-south.atracker.cloud.ibm.com

Configuring an endpoint gateway

To configure a virtual private endpoint gateway, follow these steps:

  1. List the available services, including IBM Cloud infrastructure services available (by default) for all VPC users.
  2. Create an endpoint gateway for Activity Tracker Event Routing that you want to be privately available to the VPC.
  3. Bind a reserved IP address to the endpoint gateway.
  4. View the created VPE gateways associated with Activity Tracker Event Routing. For more information, see Viewing details of an endpoint gateway.

Now your virtual server instances in the VPC can access your Activity Tracker Event Routing instance privately through it.

Using your VPE for Activity Tracker Event Routing

After you create an endpoint gateway for Activity Tracker Event Routing, you can use the VPE with the VPC API.

Using the VPE with the VPC API

After creating an endpoint gateway for the Activity Tracker Event Routing service, use the service endpoints FQDN private.<REGION>.atracker.cloud.ibm.com in the URL to access the service. For example:

curl https://private.au-syd.atracker.cloud.ibm.com/api/v2/targets' -H "Authorization: Bearer $iam_token"