All Products
Search

This Product

    API Gateway:Create a service

    Document Center

    API Gateway:Create a service

    Last Updated:Jun 03, 2026

    Add a service to a gateway to register its endpoint. Cloud-native API Gateway supports multiple service sources, including ACK, MSE Nacos, fixed addresses, DNS domain names, and Function Compute (FC).

    Procedure

    1. Log on to the API Gateway console.

    2. In the left-side navigation pane, click Cloud-native API Gateway > Instance. In the top navigation bar, select a region.

    3. On the Instance page, click the target instance ID.

    4. In the navigation pane on the left, choose Service, and click Create Service. In the Create Service panel, select a Service Source, configure its parameters, and then click OK.

    Note

    Cloud-native API Gateway does not rewrite the Host header when forwarding requests to a domain-name-based backend service. To rewrite the Host header, Configure an HTTP rewrite policy.

    Service parameters

    Service source

    Parameter

    Description

    ACK

    Note

    The gateway fetches services from an ACK or ACK Serverless cluster and registers them with their backend node addresses.

    Namespace

    Namespace of the selected cluster. Services in the arms-prom, kube-system, and mse-pilot namespaces are hidden by default.

    Services

    Select a service. Services whose names start with consumers are hidden by default.

    MSE Nacos

    Namespace

    Namespace in the MSE Nacos instance.

    Services

    Select a service. Services whose names start with consumers are hidden by default.

    Function Compute

    Backend Services

    Function list

    Select a function.

    Version or alias

    Select a version or alias for the function.

    SAE Kubernetes

    Namespace

    Namespace of the selected cluster.

    Services

    Select a service.

    Fixed Address

    Note

    Use this source type if the service does not use a service discovery mechanism. You must manually specify backend node addresses.

    Service Name

    Custom name for the service.

    Service URL

    Backend node addresses in the format <Backend node IP>:<Service port>. One address per line.

    TLS Mode

    TLS mode for backend communication. Default: disabled.

    • Disable: No TLS.

    • One-way TLS: Access the service over HTTPS.

    • mTLS: Mutual authentication required.

    DNS Domain Name

    Note

    The gateway resolves DNS entries to obtain backend service endpoints.

    Service Name

    Custom name for the service.

    Service URL

    Backend node addresses in the format <Backend node IP>:<Service port>. One address per line.

    TLS Mode

    TLS mode for backend communication. Default: disabled.

    • Disable: No TLS.

    • One-way TLS: Access the service over HTTPS.

    • mTLS: Mutual authentication required.

    CloudFlow

    Important

    • Requires gateway instance version 2.1.8 or later. Upgrade your instance if needed.

    • After creation, the system adds an HTTP rewrite policy to the API's inbound processing policy that redirects to /. This policy cannot be modified or deleted.

    • CloudFlow supports only single-service scenarios.

    Workflow

    Select an existing CloudFlow.

    Invocation Method

    Invocation mode:

    • StartExecution (asynchronous): Standard-mode workflows support only asynchronous invocation.

    • StartSyncExecution (synchronous): Express-mode workflows support only synchronous invocation.

    Verify the result

    On the Services tab, confirm the new service appears with the correct Service Name, Service URL, and Service Source.

    Related topics

    After you create a service, you can manage it from the Manage services page.