Before you use cloud-native gateways, you must create a cloud-native gateway and specify the microservice environment that you use. This way, the cloud-native gateway can interoperate with the microservice environment.
Procedure
Log on to the MSE console. In the top navigation bar, select a region.
In the left-side navigation pane, choose .
On the Gateways page, click Create Gateway.
On the buy page, configure the parameters and click Buy Now.
The following table describes the parameters that you must configure to create a cloud-native gateway. Parameter
Description
Billing Method
Select Subscription or Pay-as-you-go.
Region
Select the region in which you want to create the gateway.
Gateway Name
Enter a name for the gateway. The name must be 1 to 64 characters in length. We recommend that you configure the gateway name based on the environment or the type of your business, such as test or order-prod.
Gateway Engine Specifications
Select the specifications of the gateway engine. You can select one of the following specifications: 2 Cores, 4 GB, 4 Cores, 8 GB, 8 Cores, 16 GB, and 16 Cores, 32 GB.
Gateway Nodes
Specify the number of gateway nodes. If your gateway is deployed in a production environment, we recommend that you configure at least two nodes.
NoteA single-node gateway may result in business interruptions. We recommend that you do not configure a single-node gateway.
Resource Group
Select a resource group.
VPC
Select the virtual private cloud (VPC) in which the backend services are deployed.
vSwitch Location
Select the vSwitch location.
Zone
If you set vSwitch Location to Fixed Zone, you must configure Zone. Cloud-native gateways use the vSwitches in VPCs to communicate with backend services. We recommend that you select a vSwitch that is deployed in the same zone as the backend services.
vSwitch
If you set vSwitch Location to Custom Zone, you must select a vSwitch.
Internet-facing SLB Specifications
Select the specifications of an Internet-facing Server Load Balancer (SLB) instance, which can be accessed over the Internet.
Internal-facing SLB Specifications
Select the specifications of an internal-facing SLB instance.
Security Group Type
Select the security group type of your gateway. The default type is Advanced Security Group. We recommend that you select the same security group type as the Elastic Compute Service (ECS) instance on which backend services are deployed. For more information, see Overview.
Hardware Acceleration
Select Enable TLS Hardware Acceleration. If you enable Transport Layer Security (TLS) hardware acceleration, the handshake performance of TLS is doubled.
NoteTLS hardware acceleration is available only in the China (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen), and Singapore regions due to the limits on underlying hardware.
Monitoring and Alerting
By default, Application Real-Time Monitoring Service (ARMS) Prometheus is activated to collect metric data and logs of gateways, display data on dashboards, and manage alerts. You can use ARMS Prometheus free of charge.
Log Service
Select Use Log Service to activate Log Service and enable log shipping to help you analyze logs and visualize data on dashboards. For more information, see Enable log shipping for a cloud-native gateway.
Tracing Analysis
Select Use Tracing Analysis to activate Alibaba Cloud Tracing Analysis and enable the gateway tracing analysis feature. For more information, see Enable Tracing Analysis for a cloud-native gateway.
Subscription Duration
If you set Billing Method to Subscription, you must select a duration. You can select Auto-renewal to continue to use the gateway after the gateway expires.
NoteThe system may require 2 minutes to 3 minutes to create the cloud-native gateway.
Verify the result
Return to the Gateways page and check the status and configurations of the cloud-native gateway. If the gateway uses the configurations that you specified and the status of the gateway is Running, the gateway is created.