Configuring Gateway

Gateway provides route forwarding, and security management. Gateway can be used to manage request forwarding under the Dev Portal and App Portal domains and segregate management of service-level route configuration.

When the gateway receives access traffic, it determines whether it matches and decides on subsequent request forwarding based on the configured route rules.

Creating Route Rules

Procedure

Note

The Cluster Monitoring Service is part of the Cluster Management module of the Developer Studio and requires you to log in to EnOS ECP Developer Studio and switch to Cluster Management at the top left corner of the page menu.


Configuring Route Rule Basic Information

Create a new route configuration for the application by following these steps.

  1. In the project list, click on the project name to enter the project space.

  2. In the left navigation bar, select Gateway > Route.

  3. Click New Route and in the Basic Information field, complete the basic configuration information for the route.

  4. Click Complete to finish creating the new route.

Batch operation route rules

Route rules can be created through the export/import feature of the batch operation.

Configuring Route Rules

The route details page can be used for route rule authentication, traffic control and request log.

Authentication

Cloud IAM and ECP IAM authentication is currently supported: When this authentication method is configured, when the gateway receives a request that matches the route rules, it will intercept the request and issue authentication to Cloud IAM or ECP IAM to determine if the user identity in the request is valid. If the authentication does not pass, the gateway returns directly and does not continue the request to the back-end service.

Note

Authentication waiver can be set for some specific request paths that match the route rules.

Traffic Control

The maximum number of route requests can be set, and requests will be rejected if the request frequency is exceeded. Support the number of requests per second setting.

Request Log

Support for developing logging request logs based on request method, additional configuration of logging-free path list for request paths that do not need to be logged.

After opening the request, queries can be made based on the request time, request user name and request path keywords.

Note

Request path keywords: The log storage component will index the paths by word, for example, if the path is /demo/index-app, you can try to enter demo, index, app to search.

Log queries are also no longer available after the request logging configuration is turned off.

The steps to configure and manage routing rules in Cluster Management are similar to those in Developer Studio. For details, see Configuring Gateway.