vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/vpcep/umn/vpcep_02_0301.html
Qin Ying, Fan 5f74a04a37 VPCEP UMN 20240710 version 
Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com>
Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
2024-07-29 09:26:39 +00:00

3.1 KiB
Raw Permalink Blame History

Overview

Scenarios

If you want to access a cloud service like OBS from an on-premises data center, you can connect the on-premises data center to your VPC using a VPN connection or a Direct Connect connection, and then use a VPC endpoint to access the cloud service from your VPC.

This section describes how to use a VPC endpoint to access OBS (private address) from an on-premises data center.

Figure 1 Accessing OBS (private address) from an on-premises data center

Figure 1 shows the process of connecting the on-premises data center to a VPC over VPN or Direct Connect, and then using two VPC endpoints to enable the on-premises data center to access DNS and OBS, respectively.

A VPC endpoint comes with a VPC endpoint service. Before you create a VPC endpoint, ensure that the VPC endpoint service that you want to access is available.

The following VPC endpoint services are required:

  • VPC endpoint service for DNS: resolves the OBS domain name at the on-premises data center.

    eu-de: com.t-systems.otc.eu-de.dns

  • VPC endpoint service for OBS: provides the OBS service for the on-premises data center.

    eu-de: com.t-systems.otc.eu-de.obs

Configuration Process

Figure 2 shows the process for configuring a VPC endpoint to access OBS (private address) from the on-premises data center.

Figure 2 Configuration flowchart