Help Center> API Gateway> Dedicated API Gateway User Guide (Paris Region)> API Management> Binding a Domain Name
Updated on 2023-12-20 GMT+08:00
View PDF

Binding a Domain Name

Before exposing APIs, bind independent domain names to the group to which the APIs belong, so that API callers can access these APIs. The APIs can also be accessed using the debugging domain name allocated to the group.

  • Debugging domain name (previously called "subdomain name"): The system automatically allocates a unique debugging domain name to each API group for internal testing. The domain name can be accessed 1000 times a day, and it cannot be modified.
  • Independent domain name: You can add five custom domain names for API callers to call your open APIs. There is no limit on the number of times these domain names can be accessed.
  • Groups under the same gateway cannot be bound with a same independent domain name.
  • By default, the debugging domain name of an API group can only be resolved to a server in the same VPC as the gateway. If you want to resolve the domain name to a public network, bind an EIP to the gateway.
  • If the independent domain name you select is a wildcard domain name (for example, *.aaa.com), you can use any of its subdomain names (for example, default.aaa.com and 1.aaa.com) to access all APIs in the group to which the domain name is bound.

Prerequisites

  1. There is an independent domain name available.
  2. An A record points the independent domain name to the address of the gateway. For details, see section "Adding an A Record Set" in the Domain Name Service User Guide.
  3. If the API group contains HTTPS APIs, create an SSL certificate for the independent name.

Procedure

  1. Go to the APIG console.
  2. Select a dedicated gateway at the top of the navigation pane.
  3. Choose API Management > API Groups.
  4. Click a group name.
  5. Click the Group Information tab.
  6. In the Independent Subdomain Names area, click Bind Independent Domain Name. Then configure the domain name information.

    Table 1 Independent domain name configuration

    Parameter

    Description

    Domain Name

    Domain name to be bound to the API group.

    Minimum TLS Version

    The minimum TLS version that can be used to access the domain name. TLS 1.1 and TLS 1.2 (recommended) are supported.

    This parameter applies only to HTTPS and does not take effect for HTTP and other access modes. Configure HTTPS cipher suites using the ssl_ciphers parameter on the Parameters tab.

  7. Click OK.

    If the domain name is no longer needed, click Unbind Domain Name to unbind it from the API group.

  8. (Optional) If the API group contains HTTPS APIs, bind an SSL certificate to the independent domain name.

    1. In the row that contains the domain name, click Select SSL Certificate.
    1. Select an SSL certificate and click OK.
      • If no SSL certificate is available, click Create SSL Certificate to create one. For details, see SSL Certificates.

Troubleshooting

  • Failure in binding an independent domain name: It already exists or is not CNAMEd to the debugging domain name of the API group.
  • Failure in binding an SSL certificate: The domain name used to generate the SSL certificate is different from the target independent domain name.

Follow-Up Operations

After binding independent domain names to the API group, create APIs in the group to selectively expose backend capabilities. For details, see Creating an API.

Parent topic: API Management