Skip to content

Latest commit

 

History

History
87 lines (73 loc) · 2.41 KB

regions.md

File metadata and controls

87 lines (73 loc) · 2.41 KB
copyright lastupdated keywords subcollection
years
2017, 2019
2019-04-03
Key Protect API endpoints, available regions
key-protect

{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:new_window: target="_blank"} {:pre: .pre} {:tip: .tip} {:note: .note} {:important: .important} {:deprecated: .deprecated}

Regions and locations

{: #regions}

You can connect your applications with the {{site.data.keyword.keymanagementservicelong}} service by specifying a regional service endpoint. {: shortdesc}

Available regions

{: #available-regions}

{{site.data.keyword.keymanagementserviceshort}} is available in the following regions and locations: The image shows the regions where the Key Protect service is available.

Service endpoints

{: #service-endpoints}

If you are managing your {{site.data.keyword.keymanagementserviceshort}} resources programmatically, see the following table to determine the API endpoints to use when you connect to the {{site.data.keyword.keymanagementserviceshort}} API:

Table 1. Shows the available endpoints for the {{site.data.keyword.keymanagementserviceshort}} API
Location Service API endpoint
Dallas us-south.kms.cloud.ibm.com
Washington DC us-east.kms.cloud.ibm.com
London eu-gb.kms.cloud.ibm.com
Frankfurt eu-de.kms.cloud.ibm.com
Sydney au-syd.kms.cloud.ibm.com
Tokyo jp-tok.kms.cloud.ibm.com

You can continue to use https://keyprotect.<region>.bluemix.net to target the service for operations, or you can update your applications with the new cloud.ibm.com endpoints. {: tip}

For more information about authenticating with {{site.data.keyword.keymanagementserviceshort}}, see Accessing the API.