Parameter | Required | Description |
Billing Modes | Yes | Yearly/Monthly subscription and Pay-as-you-go are supported. If your gateway instance needs to be used for more than one month, you are advised to use the prepaid (yearly/monthly subscription) mode. For details about the price, see Pricing. |
Gateway Configuration | Yes | For common scenarios, select Default Configuration. If you have requirements for the gateway edition, you can select Custom Configuration. |
Region. | Yes | Select the region closest to your deployed business. |
Engine Version | Yes | Open-source version of the selected gateway type, which can be 2.5.1 and 2.4.1. |
Product Edition | Yes | The Developer, Standard, and Pro Editions are supported. The Pro Edition provides advanced features, such as elastic scaling and can be used in test and production environments. For specific differences, see Specification Comparison. |
Node specification | Yes | A cloud-native gateway cluster consists of multiple nodes. Select the specification for each node here. |
Node Quantity | Yes | A cloud-native gateway cluster consists of multiple nodes. Select the number of nodes here. When the number of nodes is 2, only Random AZ can be selected. When the number of nodes is greater than or equal to 3, Random AZ and Specified AZ can be selected. (At least two AZs need to be selected, and up to three AZs can be selected.) |
Deployment Architecture | Yes | Developer Edition: intra-city single-AZ deployment. Standard or Pro Edition: intra-city three-AZ deployment. HA service registration and discovery gateway instances are provided, and intra-city multi-active is supported by default. |
Node Network | Yes | Select the Tencent Cloud VPC network where the current cloud-native gateway is deployed. |
Public Load Balancer | No | Enabling public network access will charge fees. For details about the price, see Public Network Traffic Fees. Billing Mode: By traffic usage and By bandwidth are supported. Maximum bandwidth: supports a range of 1-2048 Mbps. AZ Type: Single-AZ and Multi-AZ are supported. When Multi-AZ is selected, you need to select a primary AZ and a secondary AZ. When the primary AZ is faulty, Cloud Load Balancer (CLB) can automatically switch to the secondary AZ within a short time and restore services to ensure gateway availability. |
Log Collection | No | Enable real-time log service: Cloud Native API Gateway provides real-time logging and simple search capabilities free of charge by default. To persistently store logs for troubleshooting, audit, and other scenarios, you are advised to enable Cloud Log Service (CLS). Enable CLS: Gateway log shipping is enabled for you, and log analysis is provided. Before selecting this option, confirm that you have activated CLS. The service is provided by CLS and incurs fees. For detailed billing items, see Billing Details. |
Name | Yes | Enter the name of the current cloud-native gateway. The name can contain up to 60 characters, including uppercase and lowercase letters in Chinese and English, hyphens (-), and underscores (_). |
Description | No | Enter the description of the current cloud-native gateway. |
Resource Tag | No |
QcloudAccessForApiGateWayRoleInCloudNativeAPIGateway policy. If you do not have the required role and policy, complete the authorization in the pop-up authorization window during the creation process.フィードバック