Edge Security Acceleration:Site management

Tag overview

Tags are key-value labels that you bind to sites for classification and management.

Each tag consists of a tag key and a tag value, in the format tagKey:tagValue. For example, project:website indicates site resources for the project "website".

Tags are primarily used for:

• Resource classification and search: Categorize sites by business type, environment, or owner to quickly filter targets.

• Cost allocation: Split and analyze resource costs by tag for granular cost accounting.

• Access control: Use tags with RAM to restrict specific users or roles to sites with designated tags.

Edit tags for a site

Add, modify, or delete tags for a single site.

1. Go to Websites in the ESA console and find the target site.

2. In the Tag column of the target site, click and click Edit.

3. After completing the tag configuration, click OK to save the configuration.

Manage tags using Resource Management

You can also manage tags for multiple sites through Resource Management, view tag distribution across all ESA sites under your account, and perform batch operations.

1. Log on to the Resource Management console.

2. In the Resource Type drop-down list, select Edge Security Acceleration to view all ESA sites and their tags under the account.

3. Filter by tag key or value to locate target sites. You can then batch-add or modify tags for selected sites.

Use tags for cost allocation

Split and analyze ESA site costs by tag to track resource consumption across business lines, projects, or environments.

Recommended tag keys for cost allocation:

The workflow is as follows:

1. Bind tags to sites that need cost allocation. Ensure tag keys and values accurately identify the allocation dimension (for example, cost-center:marketing).

2. Log on to the Expenses and Costs console.

3. In the left-side navigation pane, choose Cost Analysis > Cost Details.

4. On the cost details page, select Tag as the statistical dimension and choose the tag key to analyze. The system splits costs by tag value, showing the cost proportion and trend for each dimension.

Use tags to control resource access

Use RAM tag-based policies to restrict users or roles to operating only on sites with specific tags.

Typical scenarios:

• Project isolation: Project A operators can only access sites tagged project:project-a.

• Environment isolation: Development operators can only access sites tagged env:dev, preventing changes to production sites.

Configuration steps:

1. Create a custom policy in the RAM console. Use the acs:ResourceTag condition key to limit which tagged resources can be operated. Example policy:

   {
     "Version": "1",
     "Statement": [
       {
         "Effect": "Allow",
         "Action": "esa:*",
         "Resource": "*",
         "Condition": {
           "StringEquals": {
             "acs:ResourceTag/project": "website"
           }
         }
       }
     ]
   }

2. Attach the policy to the target RAM user or group. The user can then only operate on sites matching the tag conditions.

Common ESA actions used in tag-based access control:

Why does adding a site fail?

Possible causes and solutions:

• Domain already added: The root domain or subdomain is already added through ESA or another CDN product. Confirm the domain is not used by another product.

• Insufficient permissions: Confirm the account has esa:* or esa:AddSite permissions. RAM users must be authorized by the Alibaba Cloud account.

• Domain verification failed: Add the specified TXT record as prompted and retry.

What should I do if DNS does not take effect after adding a site?

DNS propagation time depends on your access method:

• NS access: Global DNS propagation may take 0–48 hours after modifying NS records, depending on the registrar and local DNS cache.

• CNAME access: Usually takes effect within minutes to a few hours.

Can a site be recovered after deletion?

No. After deletion, all configuration is permanently removed and monitoring data is retained for only 180 days. To use the same domain again, you must re-add the site and reconfigure it from scratch. Back up important configurations (DNS records, cache policies, etc.) before deletion.