Skip to content

en-cse.md

Latest commit

 

History

History
62 lines (35 loc) · 3.8 KB

en-cse.md

File metadata and controls

62 lines (35 loc) · 3.8 KB
Raw
copyright
years
2022, 2026
lastupdated 2026-05-11
keywords event-notifications, event notifications, about event notifications, service endpoints for event notifications, network isolation in event notification
subcollection event-notifications

{{site.data.keyword.attribute-definition-list}}

Using service endpoints to privately connect to {{site.data.keyword.en_short}}

{: #en-service-connection}

To help ensure that you have enhanced control and security over your data when you use {{site.data.keyword.en_short}}, you have the option of using private routes to {{site.data.keyword.cloud}} service endpoints. Private routes are not accessible or reachable over the internet. By using the {{site.data.keyword.cloud_notm}} private service endpoints feature, you can protect your data from threats from the public network and logically extend your private network. {: shortdesc}

Before you begin

{: #en-prereq-service-endpoint}

First enable virtual routing and forwarding in your account, and then you can enable the use of {{site.data.keyword.cloud_notm}} 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 {{site.data.keyword.en_short}} instance only at its creation.

Setting up private endpoints for {{site.data.keyword.en_short}} in the UI

{: #en-endpoint-setup-ui}

After your account is enabled for VRF and service endpoints, you can provision a {{site.data.keyword.en_short}} service instance to connect over a private service endpoint.

  1. In the {{site.data.keyword.cloud_notm}} console, go to the {{site.data.keyword.en_short}} offering details page{: external}.

  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), Toronto (ca-tor), Tokyo (jp-tok), Osaka (jp-osa), Sydney (au-syd), Sao Paulo (br-sao),Montreal(ca-mon), Washington DC(us-east), Chennai(in-che) and Mumbai(in-mum) regions are 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, {{site.data.keyword.en_short}} instances accept API requests from both public and private endpoints. {: note}

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

  10. Click Create. A new service instance is created and the {{site.data.keyword.en_short}} console displayed.

Viewing your endpoint URLs

{: #en-viewing-endpoint-ui}

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