- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Public NAT Gateway Operation Guide
- Private NAT Gateway Operation Guide
- 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
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Public NAT Gateway Operation Guide
- Private NAT Gateway Operation Guide
- 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
- Service Level Agreement
- Contact Us
- Glossary
Note:
Private NAT Gateway is in beta testing and currently supports Beijing, Shanghai, Guangzhou, Chengdu, Chongqing, Hong Kong (China), Singapore, Tokyo, and Virginia. If you need to use it, please submit a ticket for request.
Billing Price
The private NAT gateways incur gateway fees. Gateway fee = Instance fee + CU (Capacity Unit) fee. Both the instance fee and CU fee are postpaid and billed hourly.
Instance fee = Instance price (USD/hour) x Usage duration (hours)
CU fee = CU price (USD/unit/hour) x Number of CUs (units) x Usage duration (hours). The number of CUs is calculated based on the maximum number of CUs consumed per hour:
Number of CUs = MAX[number of CUs for hourly active connections, number of CUs for hourly new connections, number of CUs for hourly traffic processed]
Gateway Fee | Region | Unit Price (USD/unit/hour) | Transaction Unit Price for New Purchase (USD/unit/hour) |
Instance fee/CU fee | Guangzhou/Beijing/Shanghai/Chengdu/Chongqing/Hong Kong (China) | 0.034 | 0.0289 |
| Tokyo/Singapore/Virginia | 0.043 | 0.03655 |
CU is a performance capacity unit calculated based on the actual performance metrics consumed by the gateway per hour. It is used to measure various metrics involved in traffic processing by the private NAT gateway. The CU performance metrics are shown in the table below:
Metric Name | CU Coefficient | Description | Calculation Formula for the Number of CUs per Hour |
Active connections (conns) | 10,000 | The number of active connections accommodated simultaneously. During a billing cycle, the system records the number of active connections per minute for the NAT gateway, and then divides the maximum number of active connections per minute by the CU coefficient to obtain the number of CUs for hourly active connections. | Number of CUs for hourly active connections = Maximum number of active connections/CU coefficient |
New connections (cps) | 1,000 | The number of new connections per second. During a billing cycle, the system records the number of new connections per second for the NAT gateway, and then divides the maximum number of new connections per second by the CU coefficient to obtain the number of CUs for hourly new connections. | Number of CUs for hourly new connections = Maximum number of new connections/CU coefficient |
Traffic processed (bytes) | 1 GB | The quantity of the bytes processed by the NAT gateway, including outbound and inbound traffic (measured in GB). During a billing cycle, the system records the total traffic (outbound and inbound) processed by the NAT gateway, and then divides the total traffic by the CU coefficient to obtain the number of CUs for hourly processed traffic. | Number of CUs for hourly processed traffic = Total processed traffic/CU coefficient. |
Note:
The following policies became effective from 00:00:00 on June 1, 2023:
Newly purchased private NAT gateways: The transaction unit prices for instance fees and CU fees on the official website are all reduced by 15%.
Existing private NAT gateways: The price remains unchanged.
This price reduction is valid for a long term. Any subsequent changes will be announced in advance.
Billing Example
For example, you purchased a private NAT gateway instance in the Guangzhou region at 07:00:00 on January 1, 2024 and deleted the instance at 07:59:59 on January 1, 2024. During the period from 07:00:00 to 07:59:59, the instance had an average of 15,000 active connections per minute and 3,000 new connections per second, and the NAT gateway processed a total of 10 GB data for requests and responses per hour. Then the fees incurred at 08:00:00 are as follows:
Instance fee = 0.034 USD/instance/hour x 1 hour x 1 instance = 0.034 USD
CU fee = 0.034 USD/unit/hour x 1 hour x 10 units = 0.34 USD
Metric Name | Calculation for the Number of CUs per Hour |
Active connections | 15,000/10,000=1.5 |
New connections | 3,000/1,000=3 |
Traffic processed | 10/1=10 |
MAX[number of CUs for hourly active connections, number of CUs for hourly new connections, number of CUs for hourly traffic processed] | 10 |
Total fee = Instance fee + CU fee = 0.034 USD + 0.34 USD = 0.374 USD
Yes
No
Was this page helpful?