This document describes how to configure application access and routing in the TEM console. You can configure forwarding rules to implement HTTP/HTTPS forwarding rules over the public network. The use cases of this feature include:
Scenarios with applications that require public network access entries, such as microservice gateway applications.
Scenarios where domain name association is needed.
Scenarios where the same domain name has different routing/forwarding paths.
Scenarios where different domain names need to point to the same application.
2. On the Environment page, select a deployment region and click View Details under the target environment block to go to the environment details page.
3. Click the Access Management tab on the top, click Create, and enter the forwarding rule name.
Protocol and Port: HTTP:80 and HTTPS:443 are supported, and HTTPS domain names can be bound to certificates.
Forwarding Configuration:
Domain Name: existing domain names can be bound. If there are no domain names, you will be assigned an IPv4 IP by default.
Path: the default value is "/". You can configure according to the actual situation.
Backend Service: select according to the actual situation.
Service Port: select according to the actual situation.
Server Certificate: if the HTTP protocol is selected, you need to select a server certificate. If the existing certificates are not suitable, you can create one.
4. Click OK to complete the application access and routing configuration.
Related Operations
Modifying an access configuration rule: click Edit in the Operation column of the target rule and modify the access configuration in the pop-up window.
Deleting an access configuration rule: click Delete in the Operation column of the target rule and click OK in the pop-up window.
Viewing the details of a forwarding rule: click View Forwarding Rule in the Operation column of the target rule and view the details in the pop-up window.
Yes
No
Was this page helpful?