Function Compute:Custom domain configuration

3.1 Route configuration

If your application contains multiple functions, you can map different request paths to trigger different functions. For more information, see Path-matching rules.

If you need to rewrite the URI of a request that matches a specific path based on rules, see Configure a rewrite policy (in public preview).

The routing settings are managed in a table. Each rule includes the Path, Function Name, Version/Alias, and Rewrite Policy fields. For example, you can map the path /test1 to the function test-renwu, and use /* as a fallback path mapped to a default function. You can select LATEST as the version for all rules.

3.2 (Optional) HTTPS settings

To enable HTTPS access for the custom domain name, configure the following parameters.

3.3 (Optional) Authentication settings

• No Authentication: No authentication is required for HTTP requests. Anonymous access is supported, and anyone can make HTTP requests to invoke your function.

• Signature Authentication: Signature authentication is performed on HTTP requests. For more information, see Configure signature authentication for a custom domain name.

• Basic Authentication: A standard HTTP authentication method. You configure a username and password in the Function Compute console. The client must include valid credentials in the Authorization header. Access is granted only if the user information in the request matches the configured username and password. For more information, see Configure Basic authentication for a custom domain name.

• JWT Authentication: JWT authentication is performed on HTTP requests to ensure that only clients with a valid JWT can access the function. For more information, see Configure JWT authentication for a custom domain name.

• Bearer Authentication: Bearer authentication is performed on HTTP requests. You configure allowed tokens in the Function Compute console. The client must include a valid token in the Authorization header. Access is granted only if the token in the request matches a configured token. For more information, see Configure Bearer authentication for a custom domain name.

3.4 (Optional) Web application firewall settings

When enabled, the Web Application Firewall (WAF) inspects traffic to your function, filters out malicious requests, and forwards only safe traffic to the backend. This protects your function from attacks. For more information, see Enable Web Application Firewall.

3.5 (Optional) CDN settings

After you bind a custom domain name to a web application, you can use this custom domain name as the origin server domain, add an accelerated domain name, and then configure a CNAME for the accelerated domain name to enable CDN acceleration. The application deployed on Function Compute is used as the origin server to publish origin content to edge nodes. This allows end users to quickly retrieve the required content, which effectively reduces access latency and improves service quality.

1. Enable CDN acceleration, enter a custom CDN-Accelerated Domain Name, and then click Create to add it.

   For acceleration to take effect, you must manually configure the DNS record for the accelerated domain name. The Alibaba Cloud CDN service generates a CNAME value for the accelerated domain name. You must map this CNAME to your accelerated domain name.

   Important

   • The CDN acceleration feature consumes internet traffic and incurs traffic fees. For more information, see Billing overview.

   • The custom domain name and the accelerated domain name cannot be the same. To conserve domain name resources, you can configure the accelerated domain name as a subdomain name of your custom domain name. For example, if your custom domain name is example.com, you can set the accelerated domain name to fast.example.com.

2. Click your configured custom domain name. On the details page, in the CDN Acceleration Settings section, click CDN Settings in the Actions column. This redirects you to the Alibaba Cloud CDN console, where you can find the CNAME for your accelerated domain name.

   The CNAME uses the format Accelerated domain name.w.kunlun**.com, for example, fast.example.com.w.kunlunle.com.

3. Log on to the Alibaba Cloud DNS console, find your custom domain name, and create a DNS record that points the accelerated domain name to the assigned CNAME to enable acceleration. For more information, see Add a DNS record.

   Set Record Type to CNAME - Map a domain name to another domain name.

   Set Hostname to the first part of the subdomain name (in this example, fast). Set Record Value to the CNAME value for the accelerated domain name that you obtained in the previous step.

3.6 (Optional) CORS configuration

You can configure Cross-Origin Resource Sharing (CORS) for a custom domain name by calling the UpdateCustomDomain API operation. For more information, see Handle CORS requests.

4.1 Verify custom domain access

• Method 1: Use the curl URL command. Example: curl example.com/login.

• Method 2: Use a web browser.

  Enter the request URL in the address bar and press Enter to verify that the target function is invoked.

4.2 (Optional) Verify the accelerated domain

In a browser, use the accelerated domain name that you configured in Step 3.5 (Optional) CDN settings to access the application. Then, open the developer tools and check the value of the X-Cache response header to verify that CDN acceleration is working.