In Enterprise Distributed Application Service (EDAS), when a Server Load Balancer (SLB) instance is bound to an application, it distributes access traffic to the application to multiple backend Elastic Compute Service (ECS) instances based on the forwarding rules. SLB improves the service capability and availability of applications. The changes you made to the SLB instance bound to an application in the EDAS console can be synchronized to the SLB console in real time. You do not need to make the changes in the SLB console again.

Bind an SLB instance to an application in an ECS cluster

Applications in the ECS cluster support layer-4 (TCP) and layer-7 (HTTP or HTTPS) listening. You can choose the listening protocol according to the application scenario.
  • TCP is applicable to scenarios that require high reliability and data accuracy but can tolerate low speed, such as file transmission, email sending or receiving, and remote logon.
  • HTTP is applicable to applications that need to identify data content, such as web applications and small mobile games.
  • HTTPS is applicable to applications that require encrypted transmission to prevent unauthorized access.

Bind an SLB instance to an application

Bind an SLB instance to your application and set the traffic distribution rules by referring to the following tutorials: