tencent cloud

NAT Gateway

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Product Specifications
Relevant Products
Purchase Guide
Public NAT Gateway Billing Overview
Private NAT Gateway Operation Guide
Purchasing in the Console
Overdue Payment and Service Expiration Policies
Getting Started
Public NAT Gateway Operation Guide
Modifying NAT Gateway Configuration
Managing EIPs of NAT Gateway
Routing to NAT Gateway
Managing SNAT Rules
Managing Port Forwarding Rules
Public NAT Usage Limits
NAT Gateway Flow Logs
Binding with Anti-DDoS Pro
Monitoring and Alarms
Deleting NAT Gateway
Adjusting the Priorities of NAT Gateways and EIPs
Private NAT Gateway Operation Guide
Creating and Managing a NAT Gateway
Configuring a Route to Private NAT Gateway
Managing SNAT Rules
Managing DNAT Rules
Cloud Access Management
Practical Tutorial
Enabling Cross-VPC Access to Public Network via Standard NAT Gateway
Enabling Mutual Access between a Specified VPC Subnet and Public Network Resources via Private NAT Gateway
Enabling Secure Mutual Access with Public Network via Public CLB and NAT Gateway
Adjusting the Priorities of NAT Gateways and EIPs
API Documentation
FAQ
Billing
Concepts
Features
Service Level Agreement
Contact Us
Glossary
DocumentaçãoNAT GatewayProduct IntroductionRelevant Products

Relevant Products

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-10-20 16:51:48
This document describes the network products related to NAT Gateway.

EIP

The NAT Gateway and the EIP are two ways for a CVM instance to access the public network. You can use either or both of them in your public network access architecture.

Method 1: using NAT Gateway only

The CVM instance without any public IP uses the public IP of the NAT Gateway to access the public network. Traffic to the public network is forwarded to the NAT Gateway via the private network.

Method 2: using the EIP only

The CVM instance uses EIPs to access the public network without any NAT Gateway. Traffic to the public network will be forwarded from the EIP.

Method 3: using NAT Gateway and EIP

Note:
For more information about EIPs, see Elastic IP.
The CVM instance is bound with an EIP, and the route table directs all traffic from the subnet to the public network to the NAT Gateway.
All traffic from the CVM instance to the public network uses the NAT Gateway through the private network, and the response packets are returned through the NAT Gateway. If you want to use the EIP to access the public network, you can adjust priorities of NAT Gateways and EIPs.
When the traffic from the public network uses the EIPs to access CVM, the CVM response packets are returned through the EIPs.

Bandwidth Package

If your NAT Gateway is bound with multiple EIPs, you can add them to the IP bandwidth package to share the bandwidth and save public network costs. For more information, see Product Overview.

Other Products

The table below lists other products related to the NAT Gateway:
Product Name
Relationship
The NAT Gateway and the EIP are two ways for CVM instances to access the Internet.
The EIP and the NAT Gateway are two ways for CVM instances to access the Internet.
NAT Gateway is part of VPC.
After creating a NAT Gateway, you need to configure routing policies to direct the subnet traffic to the NAT Gateway.
A public gateway is a CVM with the forwarding feature enabled and can be accessed by NAT Gateway.
Anti-DDoS Pro instance can be bound to a NAT Gateway to defend against DDoS and CC attacks.
Use network ACL to finely control the inbound and outbound traffic of subnets.
Anterior: Product SpecificationsPróximo: Public NAT Gateway Billing Overview

Ajuda e Suporte

Esta página foi útil?

comentários