Help Center/ NAT Gateway/ User Guide (Paris Region) / Getting Started/ Using Private NAT Gateways to Enable Communications Between Cloud and On-premises Networks/ Overview

Updated on 2024-03-30 GMT+08:00

View PDF

Overview

You can use a private NAT gateway to enable communications between cloud and on-premises networks.

The following figure shows how a private NAT gateway enables ECSs in a VPC to communicate with your on-premises data center that has been connected to the cloud using Direct Connect.

Figure 1 Networking diagram

In this example, the CIDR block of your on-premises data center is 10.0.0.0/24. The subnet of the transit VPC in the region is 10.1.0.0/24.

How networks are connected to each other

Your on-premises data center is connected to the transit VPC using Direct Connect.
The VPC where your services are deployed is connected to the transit VPC using a private NAT gateway.

This following figure shows the procedure.

Figure 2 Procedure

Parent topic: Using Private NAT Gateways to Enable Communications Between Cloud and On-premises Networks

Previous topic: Using Private NAT Gateways to Enable Communications Between Cloud and On-premises Networks

Next topic: Step 1: Create a Service VPC and a Transit VPC

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.