Create a Cloud-native Gateway Serverless instance
This topic describes how to create a Cloud-native Gateway Serverless instance.
Billing
The configuration fee displayed on the creation page is the price for the minimum workload. During runtime, the instance is billed based on your actual usage. For more information, see Serverless instance billing overview.
Procedure
Go to the Serverless instance creation page.
On the Cloud-native Gateway (Serverless) page, configure the following parameters.
NoteAn MSE Serverless instance is a multi-node cluster deployed across multiple availability zones to ensure high availability. Resources are automatically scaled based on workload. Unlike regular instances, you do not need to specify the specifications or number of nodes on the creation page.
Parameter
Description
Region
Select the region where you want to deploy the instance.
NoteMSE Serverless instances are currently available only in some regions in Chinese mainland. For other regions, use a regular instance.
Gateway name
Enter a custom name for the gateway. The name can be up to 64 characters long. We recommend naming it after the environment or business domain, such as
testororder-prod.Resource group
Select a resource group. Resource groups enable hierarchical resource management for multiple users and projects.
VPC
Select the VPC where your backend services run. For example, if applications access services in a Kubernetes cluster through the gateway, select the same VPC as the Kubernetes cluster. If applications access services registered in Nacos through the gateway, select the same VPC as the Nacos instance.
Load balancer type
Select Network Load Balancer (NLB) or Classic Load Balancer (CLB).
vSwitch location
Choose between Manual Selection or Automatic Assignment:
Manual Selection: You must select the availability zone and vSwitch.
Automatic Assignment: You must select a vSwitch.
Availability zone and vSwitch
Select the availability zones and vSwitches where you want to deploy the gateway and NLB instance. You must add at least two availability zones and vSwitches. Selecting an availability zone different from that of your backend services does not affect your services.
vSwitch
Select an existing vSwitch in the VPC or create a new vSwitch.
Network access type
Public: Select this option if your applications access the gateway over the public network. This creates a public-facing NLB instance.
Private: Select this option if your applications access the gateway from within the VPC. This creates a private NLB instance.
Private and public: Select this option if your applications access the gateway over both the public network and from within the VPC. This creates both a private and a public-facing NLB instance.
NoteThe billing for Cloud-native Gateway does not include NLB fees. Alibaba Cloud load balancer products are billed separately. You can change the NLB instance on the gateway instance's basic information page.
Security group type
Select the type of security group for the gateway. The default is Enterprise Security Group. We recommend using the same security group type as the ECS instances that host your backend services. For more information, see Security group overview.
Gateway monitoring
MSE uses Managed Service for Prometheus to collect instance metrics and provide monitoring dashboards. This feature uses a free instance of Prometheus for cloud services.
Alert configuration
MSE uses Application Real-Time Monitoring Service (ARMS) to provide alerting.
After you select Configure Alerts Using Default Template, the system automatically configures key alert rules and sends notifications to the selected contact group when an alert is triggered.
Alert contact group
If you select Alert Configuration > Configure Alerts Using Default Template, you must select a contact group to receive these alert notifications.
Log Service
Select Use Log Service (SLS) to enable gateway log delivery to Log Service (SLS). This provides log analysis and dashboards. For more information, see Enable gateway log delivery.
Tracing
Select Use Managed Service for OpenTelemetry to enable gateway tracing with Managed Service for OpenTelemetry. This helps you quickly diagnose application performance bottlenecks. For more information, see Enable gateway tracing.
Engine version upgrade
During the maintenance window, MSE Serverless instances automatically upgrade the engine to a newer minor version. You can reset the maintenance window on the instance's basic information page.
Service-linked role
The Cloud-native Gateway automatically creates this role to access other Alibaba Cloud services.
Click Buy Now.
In the Service Agreement section, read and accept the agreement. After confirming the configurations are correct, click Activate Now.
Related topics
To learn more about MSE Serverless instances, see Introduction to MSE Serverless instances.
For guidance on choosing a Cloud-native Gateway instance, see Instance type selection.