Help Center/ Cloud Service Engine/ User Guide/ ServiceComb Engines/ Managing ServiceComb Engines/ Managing Public Network Access for a ServiceComb Engine
Updated on 2026-07-13 GMT+08:00
View PDF
Share

Managing Public Network Access for a ServiceComb Engine

The ServiceComb engine supports public network access, which helps expand the microservice architecture from a closed environment on the intranet to an open ecosystem on the public network. This not only meets the requirements of cross-cloud collaboration, but also improves the system elasticity, scalability, and DR capabilities through the openness of the technical architecture.

Constraints

  • ServiceComb engines with security authentication disabled do not have the authentication and authorization capabilities. Opening those engines to the public network may cause security risks and increases the system vulnerability. For example, data assets such as configurations and service information may be stolen.
  • Do not use this function in a production environment or a network environment with high security requirements.

Prerequisites

An EIP has been created. For details about how to create an EIP, see Assigning an EIP.

Binding an EIP

ServiceComb engines that are bound with EIPs can be accessed from the public network.

  1. Click the target engine.
  2. In the Network Configuration and Security area, click Bind EIP.

  3. Read the security risk prompt in the displayed dialog box and select I understand the security risks.
  4. In the EIP drop-down list, select the EIP to be bound. You can only select an EIP in the same enterprise project as the ServiceComb engine.
  5. Click OK.

Unbinding an EIP

If an EIP has been bound to a ServiceComb engine, you can unbind the EIP from the engine to disable the public network access to the engine.

  1. Click the target engine.
  2. In the Network Configuration and Security area, click Unbind EIP.

  3. In the displayed dialog box, click OK.