IBM Cloud Docs
Using service endpoints to privately connect to Event Notifications

Using service endpoints to privately connect to Event Notifications

To ensure that you have enhanced control and security over your data when you use Event Notifications, you have the option of using private routes to IBM Cloud® service endpoints. Private routes are not accessible or reachable over the internet. By using the IBM Cloud private service endpoints feature, you can protect your data from threats from the public network and logically extend your private network.

Before you begin

You must first enable virtual routing and forwarding in your account, and then you can enable the use of IBM Cloud private service endpoints. For more information about setting up your account to support the private connectivity option, see Enabling VRF and service endpoints.

Keep in mind the following considerations:

  • You can select a service endpoint option for a Event Notifications instance only at its creation.
  • The Event Notifications service UI is not accessible for Private only instances.

Setting up private endpoints for Event Notifications in the UI

After your account is enabled for VRF and service endpoints, you can provision a Event Notifications service instance to connect over a private service endpoint.

  1. In the IBM Cloud console, go to the Event Notifications offering details page.

  2. In the Create tab, select the location that represents the geographic area (Region) where you want to provision your instance. Currently, Dallas (us-south), London (eu-gb), Frankfurt (eu-de), Madrid (eu-es) and Sydney (au-syd) region is supported.

  3. Select a pricing plan - Based on your business requirements, select a pricing plan: Lite, and Standard.

  4. Configure your resource by providing a Service name for your instance, or use the preset name.

  5. Select a resource group - The resource group selection helps how you want resources to be organized in your account. The resource group that you select cannot be changed after the service instance is created.

  6. Optionally, define Tags to help you to identify and organize the instance in your account. If your tags are billing related, consider writing tags as key:value pairs to help group-related tags, such as costctr:124.

  7. Optionally, define Access management tags that are required to apply flexible access policies on specific resources. For example, access:dev, proj:version-1.

  8. For the Service endpoints, from the list of endpoint options, select Both public & private network.

    By default, Event Notifications instances accept API requests from both public and private endpoints.

  9. Accept the licensing agreements and terms by clicking the checkbox.

  10. Click Create. A new service instance is created and the Event Notifications console displayed.

Viewing your endpoint URLs

The service endpoint URLs are different for private and public network connections. For more information about your service endpoint URLs, see Regions and endpoints.