All Products
Search

This Product

    Microservices Engine:Create a cloud-native gateway

    Document Center

    Microservices Engine:Create a cloud-native gateway

    Last Updated:Sep 10, 2024

    Before you can use a cloud-native gateway, you must create a cloud-native gateway and specify the microservice environment that you use. This way, the cloud-native gateway can interoperate with your microservice environment.

    Procedure

    1. Log on to the MSE console. In the top navigation bar, select a region.

    2. In the left-side navigation pane, choose Cloud-native Gateway > Gateways.

    3. In the upper-left corner of the Gateways page, click Create Gateway.

    4. On the buy page, configure the parameters and click Buy Now.

      Parameter

      Description

      Billing Method

      Select Subscription or Pay-as-you-go.

      Region

      Select the region in which you want to deploy the gateway.

      Gateway Name

      Enter a name for the gateway. The name length cannot exceed 64 characters. 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 2 Cores, 4 GB, 4 Cores, 8 GB, 8 Cores, 16 GB, or 16 Cores, 32 GB based on your business requirements.

      Gateway Nodes

      Specify the number of gateway nodes. If you want to deploy the gateway in a production environment, we recommend that you configure at least two nodes.

      Note

      A single-node gateway may result in business interruptions. We recommend that you do not configure a single-node gateway.

      Hardware Acceleration

      Select Enable TLS Hardware Accelerator to enable TLS hardware acceleration. This way, the handshake performance of TLS is doubled.

      Note

      TLS hardware acceleration is available only in specific regions due to the limits on underlying hardware. For more information about the supported regions, see Limits.

      Resource Group

      Select a resource group from the drop-down list.

      VPC

      Select the virtual private cloud (VPC) in which the backend services are deployed.

      Gateway Ingress Type

      • NLB: For more information, see What is NLB?

      • CLB: For more information, see Billing overview.

      • None: Server Load Balancer (SLB) instances are not used as the gateway ingress. You can change the gateway ingress type in the MSE console.

      Gateway Ingress Billing Method

      Pay By Usage is used.

      Zone Location

      Select Manual Selection or Automatic Allocation.

      • Manual Selection: Select Zone and then select a vSwitch.

      • Automatic Allocation: Select a vSwitch.

      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

      Select a vSwitch in the VPC or create a vSwitch.

      Network Type

      • Internet: Select this option if you want to access the gateway over the Internet.

      • Private Network: Select this option if you want to access the gateway over a VPC.

      • Private Network and Internet: Select this option if you want to access the gateway over both the Internet and a VPC. The system automatically creates an Internet-facing SLB instance and an internal-facing SLB based on the selected SLB instance type.

      Security Group Type

      Select a security group type for 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.

      Gateway Monitoring

      By default, Managed Service for Prometheus is activated. This service collects the metric data of gateways, displays data on dashboards, and manages alerts. You can use Managed Service for 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 Managed Service for OpenTelemetry to activate Alibaba Cloud Managed Service for OpenTelemetry and enable the gateway tracing analysis feature. For more information, see Enable Tracing Analysis for a cloud-native gateway.

      Service-linked Role

      A service-linked role is automatically created to allow the MSE cloud-native gateway to access other Alibaba Cloud services.

      Duration

      If you select Subscription for Billing Method, you must select a duration. You can select Auto-renewal to continue to use the gateway after the gateway expires.

      Note

      The 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.