Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- What's New
- Function Overview
- Service Overview
-
Getting Started
- Allowing a Private Network to Access the Internet Using SNAT
- Allowing Internet Users to Access a Service in a Private Network Using DNAT
- Allowing On-Premises Servers to Communicate with the Internet
- Using Private NAT Gateways to Enable Communications Between Cloud and On-premises Networks
- Using Multiple Public NAT Gateways Together in Performance-Demanding Scenarios
- Change History
-
User Guide
- Public NAT Gateways
- Private NAT Gateways
- Managing NAT Gateway Tags
- Monitoring
- Auditing
- Change History
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- V2 APIs of Public NAT Gateways
- API v2.0
- Private Nat API
- Permissions Policies and Supported Actions
- Common Parameters
- Change History
-
FAQs
-
Public NAT Gateways
- What Is the Relationship Between a VPC, Public NAT Gateway, EIP Bandwidth, and ECS?
- How Does a Public NAT Gateway Offer High Availability?
- Which Ports Cannot Be Accessed?
- What Are the Differences Between Using a Public NAT Gateway and Using an EIP for an ECS?
- What Should I Do If I Fail to Access the Internet Through a Public NAT Gateway?
- Can I Change the VPC for a Public NAT Gateway?
- Does Public NAT Gateway Support IPv6 Addresses?
- What Security Policies Can I Configure to Implement Access Control If I Use a Public NAT Gateway?
- What Can I Do If Connection Between My Servers and the Internet Fails After I Add SNAT and DNAT Rules?
-
Private NAT Gateways
- How Do I Troubleshoot a Network Failure After a Private NAT Gateway Is Configured?
- How Many Private NAT Gateways Can I Create in a VPC?
- Can I Increase the Numbers of SNAT and DNAT Rules Supported by a Private NAT Gateway?
- Can an SNAT and DNAT Rule of a Private NAT Gateway Share the Same Transit IP Address?
- Can Private NAT Gateways Translate On-premises IP Addresses Connected to the Cloud Through Direct Connect?
- What Are the Differences Between Private NAT Gateways and Public NAT Gateways?
- How Is Private NAT Gateway Billed?
- Can a Private NAT Gateway Be Used Across Accounts?
-
SNAT Rules
- Why Do I Need SNAT?
- What Are SNAT Connections?
- What Is the Bandwidth of a Public NAT Gateway Used by a Server to Access the Internet? How Do I Configure the Bandwidth?
- How Do I Resolve Packet Loss or Connection Failure Issues When Using a NAT Gateway?
- What Should I Do If My ECS Fails to Access a Server on the Public Network Through a Public NAT Gateway?
- What Are the Relationships and Differences Between the CIDR Blocks in a NAT Gateway and in an SNAT Rule?
- DNAT Rules
-
Public NAT Gateways
- SDK Reference
Show all
Function Overview
-
Public NAT Gateway
-
Public NAT gateways provide NAT for servers in a VPC or on-premises servers that connect to the cloud through Direct Connect or Virtual Private Network (VPN), allowing multiple servers to share EIPs for Internet connectivity.
Public NAT Gateway: All regions
-
-
Public NAT Gateway-Pay-per-use Billing Mode
-
Public NAT gateways are billed based on the public NAT gateway type and service duration. There are four types of public NAT gateways: small, medium, large, and ultra-large. Public NAT gateways can be billed on a pay-per-use (day) basis.
Public NAT Gateway: All regions
-
-
SNAT Rule
-
Public NAT gateways support source NAT (SNAT) and destination NAT (DNAT).
SNAT translates private IP addresses into EIPs, allowing servers within an AZ or across multiple AZs in a VPC to share EIPs to access the Internet.
DNAT enables multiple servers within an AZ or across multiple AZs in a VPC to share EIPs to provide services accessible from the Internet. With an EIP, a NAT gateway forwards the Internet requests from only a specific port and over a specific protocol to a specific port of a server, or it can forward all requests to the server regardless of which port they originated on.
Public NAT Gateway: All regions
Private NAT Gateway: AP-Bangkok, AP-Singapore, China-Hong Kong, CN North-Beijing4, CN East-Shanghai1, CN East-Shanghai2, CN South-Guangzhou, Africa-Johannesburg, and Southwest-Guiyang1
-
-
DNAT Rule
-
Public NAT gateways support source NAT (SNAT) and destination NAT (DNAT).
SNAT translates private IP addresses into EIPs, allowing servers within an AZ or across multiple AZs in a VPC to share EIPs to access the Internet.
DNAT enables multiple servers within an AZ or across multiple AZs in a VPC to share EIPs to provide services accessible from the Internet. With an EIP, a NAT gateway forwards the Internet requests from only a specific port and over a specific protocol to a specific port of a server, or it can forward all requests to the server regardless of which port they originated on.
Public NAT Gateway: All regions
Private NAT Gateway: AP-Bangkok, AP-Singapore, China-Hong Kong, CN North-Beijing4, CN East-Shanghai1, CN East-Shanghai2, CN South-Guangzhou, Africa-Johannesburg, and Southwest-Guiyang1
-
-
Enterprise Project
-
NAT Gateway resources can be managed by enterprise project. You can add NAT Gateway resources to or remove NAT Gateway resources from an enterprise project. You must manage NAT Gateway resources based on the permissions granted with the user group you belong to.
Public NAT Gateway: All regions
Private NAT Gateway: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, CN Southwest-Guiyang1, China-Hong Kong, AP-Bangkok, AP-Singapore, and Africa-Johannesburg
-
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.