DocsICP FilingConsole
官方文档
首页

Create an MSE cloud-native gateway

更新时间：
复制 MD 格式
产品详情
我的收藏

MSE cloud-native gateways are compatible with Kubernetes Ingresses and support service discovery from various sources, such as Container Service for Kubernetes (ACK) and Nacos. They also provide comprehensive security and O&M capabilities. This topic describes how to create an MSE cloud-native gateway.

Procedure

  1. Go to the purchase page for the MSE cloud-native gateway.

    • From the MSE product page:

      1. Log in to the MSE product page.

      2. On the product page, click Buy Now and select the Cloud-native Gateway tab.

    • From the MSE console:

      1. Log in to the MSE console.

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

      3. In the top navigation bar, select a region.

      4. On the Gateways page, click Create Gateway in the upper-left corner.

  2. On the purchase page, configure the parameters and click Buy Now.

    Parameter

    Description

    Product Type

    Supports the subscription and Pay-as-you-go billing methods. For more information about pricing, see Billing of instances.

    Region

    Select the region where you want to deploy the gateway.

    Gateway Name

    Enter a name for the gateway. We recommend naming it based on the environment or business domain, such as test or order-prod. The name can be up to 64 characters long.

    Node specifications/Gateway instance specifications

    Select the engine specifications based on your requirements. Options include 2 Cores, 4 GB, 4 Cores, 8 GB, 8 Cores, 16 GB, and 16 Cores, 32 GB. For more information, see Performance metrics of standard instances.

    Number of nodes/Gateway nodes

    Select the number of gateway nodes. For production environments, we recommend using at least two nodes.

    Note

    A single-node gateway lacks high availability and is not recommended for production environments.

    Hardware acceleration

    Select Enable TLS Hardware Acceleration to use dedicated hardware for TLS handshake acceleration, improving performance by up to 100%.

    Note

    Due to hardware limitations, this feature is available only in specific regions. For more information, see Limits.

    Resource group

    Select a resource group.

    VPC

    Select the VPC where your backend services are located.

    Note

    When you select a VPC, the system indicates whether a container or Nacos cluster exists in the VPC to prevent incorrect selections.

    Gateway ingress type
    Note

    If the gateway ingress type is Network Load Balancer (NLB) or Classic Load Balancer (CLB), you can attach up to 20 load balancers to a single gateway instance.

    Gateway ingress billing method

    Only Pay by Usage is supported.

    Zone location

    Select Manual Selection or Automatic Allocation.

    • Manual Selection: You must select a zone and vSwitch.

    • Automatic Allocation: You must select a vSwitch.

    Zone and vSwitch

    The gateway uses a vSwitch within the VPC to communicate with backend services. For optimal performance, select a vSwitch in the same zone as your backend services.

    vSwitch

    Select a vSwitch in the VPC or create a new vSwitch.

    Network type

    • Internet: Assigns a public IP address to the gateway, allowing access from the internet.

    • Private Network: Assigns a private IP address within the VPC.

    • Private Network and Internet: Select this option to access the gateway instance from both the internet and a private network. The system automatically creates an internet-facing and an internal-facing load balancer of the selected type.

    Security group type

    Select the security group type for the gateway. The default is Advanced Security Group. We recommend using the same security group type as the ECS instances that host your backend services to ensure consistent security policies. For more information, see Security group overview.

    Gateway monitoring

    By default, Managed Service for Prometheus is enabled to collect gateway metrics, provide monitoring dashboards, and manage alerts. This feature is free of charge.

    log service

    Select Use Log Service (SLS) to ship gateway logs to Simple Log Service (SLS). This provides log analysis and dashboards. For more information, see Enable gateway log shipping.

    Tracing analysis

    Select Use Managed Service for OpenTelemetry to activate the tracing analysis feature for the gateway. For more information, see Enable gateway tracing analysis.

    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 the subscription billing method, you must specify a duration. You can also select Auto-renewal to automatically renew your subscription and prevent service interruptions.
    Note

    Gateway creation takes 2 to 3 minutes.

Previous：Cloud-native gatewaysNext：Upgrade an MSE cloud-native gateway