Edge Security Acceleration:Manage origin pools

Overview

Origin pools provide basic weighted origin fetch scheduling for multiple origin servers and can be referenced by ESA domains and TCP/UDP proxy applications. Combined with the load balancing service, you can configure various load balancing policies to improve service availability. 

Create an origin pool

1. In the ESA console, select Websites, and in the Website column, click your target site.

2. In the left navigation pane, choose Traffic > Origin Pools.

3. On the Origin Pools page, click Create Origin Pool.

4. On the Create Origin Pool page, enter a Pool Name and add at least one Origin Server.

   Parameter	Description
   Pool Name	The name of the origin pool, which cannot be changed after the pool is created. The name can be up to 200 characters long and can contain only the following characters: Lowercase letters: a-z Digits Hyphens (-), but not at the beginning or end
   Domain Name	Automatically generated by the system. The format is: [pool name].origin-pool.[your site domain].
   Origin Server-Name	A custom name for the origin server.
   Origin Server-Type	Select the type of your origin server: IP/Domain: An IPv4 address, IPv6 address, or domain name. OSS: Alibaba Cloud Object Storage Service (OSS). S3-compatible: S3-compatible storage. EAG Origin-fetch Acceleration: Origin fetch acceleration through an Edge Acceleration Gateway (EAG) instance. Note If you use S3-compatible mode, you can also fetch content from a private OSS bucket.
   Origin Server-Origin Address	Enter the address of your origin server. If you select EAG Origin-fetch Acceleration, select an EAG domain name from the drop-down list. After you select a domain name, the system displays information about the associated EAG instance.
   Origin Server-Weight and Percent	The default weight is 50. Valid values range from 0 to 100, with a minimum increment of 1. If you set the weight to 0, no origin fetch requests are sent to this origin server. Percentage: The system calculates this percentage based on the configured weights to show the traffic distribution ratio.
   Origin Server-Origin Host Header	Specifies the Host header that ESA uses for origin fetch requests to this origin server. Note If you leave this field blank, ESA uses the host policy from your DNS settings.
   Origin Server-Origin Fetch IP Version	Specifies the policy that ESA nodes use to select an IP version (IPv4 or IPv6) for origin fetch requests. The default policy is Random Poll IPv4/IPv6 Origin. Random Poll IPv4/IPv6 Origin: Meaning: When ESA performs an origin fetch, it randomly selects one IP address from all available origin server IP addresses, including IPv4 and IPv6 addresses. Use case: Your origin server supports both IPv4 and IPv6, and you want to balance the load between them. Benefit: Fully utilizes dual-stack capabilities and prevents overloading a single protocol. Prioritize IPv4 Origin: Meaning: ESA prioritizes IPv4 for origin fetches and falls back to IPv6 only if all IPv4 addresses are unavailable, such as from connection failures. Use case: Your IPv4 network is more stable or has broader coverage, or your origin server's IPv6 support is incomplete. Benefit: Maximizes compatibility with traditional deployment environments. Prioritize IPv6 Origin: Meaning: ESA prioritizes IPv6 addresses for origin fetches. It falls back to IPv4 only if all IPv6 addresses are unavailable. Use case: Your origin server fully supports IPv6, and you want to increase the proportion of IPv6 traffic, for example, to comply with national IPv6 adoption policies. Benefit: Helps increase the IPv6 usage of your origin server. Prioritize Client IP Version: Meaning: ESA matches the IP version for origin fetches to the version the client used to access the ESA node. If a client connects using IPv6, ESA prioritizes IPv6 for origin fetches. If a client connects using IPv4, ESA prioritizes IPv4 for origin fetches. Use case: You want to maintain end-to-end protocol consistency for easier debugging or to meet specific security or auditing requirements. Benefit: Simplifies traffic path tracing and ensures a more consistent experience if the origin server has a robust dual-stack implementation.

5. After you configure all origin server settings, click OK to create the origin pool.

Delete an origin pool

1. In the ESA console, select Websites, and in the Website column, click your target site.

2. In the left navigation pane, choose Traffic > Origin Pools.

3. Find the origin pool that you want to delete and click Delete.

   Note

   If a load balancer references the origin pool, you must first remove the pool from the load balancer's configuration. Failure to do so can cause traffic routing errors, service interruptions, and health check failures. For instructions, see Delete an origin pool referenced by a load balancer.

Feature availability