Using a virtual private endpoint

Before you begin

Before you target a virtual private endpoint for Key Protect:

• Ensure that you have provisioned a Virtual Private Cloud.
• Ensure that you have conducted planning for Virtual Private Endpoints.
• Ensure that correct access controls are set for your virtual private endpoint.
• Understand the limitations of having a virtual private endpoint.
• Ensure that you have created and understand how to access a VPE gateway.
• Understand how to view details of a Virtual Private Endpoint.

Virtual private endpoint settings, specifically the Internet Protocol (IP) address, may need to be manually updated during Disaster recovery and business continuity actions.

Virtual Private Service Endpoints

The following table lists regions where Key Protect service supports VPE. It also lists Key Protect endpoints supported from each region. You can connect to Key Protect service in another region using supported endpoints. For example, from the Sydney region, you can use Key Protect service in us-south region using the us-south endpoint.

When connecting to a VPE via CLI or API, you will need to specify the CRN of the region that you will use to connect to the Key Protect service. Use the table below to locate the CRN of the target region.