| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2023-12-20 |
event-notifications, event notifications, regions, endpoints, private endpoints |
event-notifications |
{{site.data.keyword.attribute-definition-list}}
{: #en-regions-endpoints}
Review region and connectivity options for interacting with {{site.data.keyword.en_full_notm}}. {: shortdesc}
{: #en-regions}
{{site.data.keyword.en_full_notm}} is available in the following regions:
- Dallas (
us-south) - London (
eu-gb) - Sydney (
au-syd) - Frankfurt (
eu-de) - Madrid (
eu-es) - Toronto (
ca-tor) - Tokyo (
jp-tok) - Osaka (
jp-osa)
You can create {{site.data.keyword.en_full_notm}} resources in one of the supported {{site.data.keyword.cloud_notm}} regions.
{: #en-service-endpoints}
{{site.data.keyword.en_short}} offers two connectivity options for interacting with its service APIs.
Public endpoints : By default, you can connect to resources in your account over the {{site.data.keyword.cloud_notm}} public network. Your data is encrypted in transit by default that uses the Transport Security Layer (TLS) 1.2 protocol.
Private endpoints : To further secure your connection, you can also enable virtual routing and forwarding (VRF) and service endpoints{: external} for your infrastructure account. When you enable VRF for your account, you can connect to {{site.data.keyword.en_short}} by using a private IP that is accessible only through the {{site.data.keyword.cloud_notm}} private network.
{: #en-public-endpoints}
The following table contains the base URLs for the {{site.data.keyword.en_full_notm}} API endpoints. When you call the API, use the URL that corresponds to the region where your service instance is deployed. Add the path for each method to form the complete API endpoint for your requests.
| Location | Endpoint URL |
|---|---|
| Dallas | https://us-south.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| London | https://eu-gb.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Sydney | https://au-syd.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Frankfurt | https://eu-de.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Madrid | https://eu-es.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Toronto | https://ca-tor.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Tokyo | https://jp-tok.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Osaka | https://jp-osa.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| {: caption="Public endpoints for interacting with {{site.data.keyword.en_short}} by using APIs" caption-side="bottom"} |
{: #en-private-endpoints}
If you need to manage your {{site.data.keyword.en_short}} resources over a private network, see the following table to determine the API endpoints to use when you connect to the {{site.data.keyword.en_short}} API.
| Region | Endpoint URL |
|---|---|
| Dallas | https://private.us-south.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| London | https://private.eu-gb.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Sydney | https://private.au-syd.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Frankfurt | https://private.eu-de.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Madrid | https://private.eu-es.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Toronto | https://private.ca-tor.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Tokyo | https://private.jp-tok.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| Osaka | https://private.jp-osa.event-notifications.cloud.ibm.com/event-notifications/v1/instances/{guid} |
| {: caption="Private endpoints for interacting with {{site.data.keyword.en_short}} by using APIs" caption-side="bottom"} |