Accessing virtual private endpoints in specific regions

Before you begin

Before you target a VPE for Key Protect:

• Make sure that you have provisioned a Virtual Private Cloud.
• Make sure that you have conducted planning for Virtual Private Endpoints.
• Make sure that you set the correct access controls for your VPE.
• Understand the limitations of having a VPE.
• Make sure that you created a VPE gateway and understand how to access it.
• Understand how to view details of a VPE.

You might need to manually update VPE settings, specifically the Internet Protocol (IP) address, during Disaster recovery and business continuity actions.

Virtual Private Service Endpoints

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

When you connect to a VPE by using the CLI or API, specify the CRN of the region that you use to connect to Key Protect. Use the following table to locate the CRN of the target region.