- What's New
- Function Overview
- Service Overview
- Billing
-
User Guide
- Enabling EdgeSec
- Site Acceleration
-
Security Protection
- Connecting a Domain Name to EdgeSec
- Dashboard
- Protection Statistics
-
Protection Policy
- Creating a Protection Policy
- Applying a Policy to Your Website
-
Configuring Protection Policies
- Configuration Guidance
- Configuring Basic Protection Rules to Defend Against Common Web Attacks
- Configuring CC Attack Protection Rules to Defend Against CC Attacks
- Configuring a Precise Protection Rule
- Creating a Reference Table to Configure Protection Metrics In Batches
- Configuring IP Address Blacklist and Whitelist Rules to Block Specified IP Addresses
- Configuring a Known Attack Source Rule
- Configuring Geolocation Access Control Rules to Block Requests from Specific Locations
- Configuring a BOT Protection Rule
- Configuring a Global Whitelist Rule to Ignore False Positives
- Configuring a Data Masking Rule
- Address Group Management
- System Management
- Permissions Management
- Key Operations Recorded by CTS
- Best Practices
-
API Reference
- Before You Start
- API Overview
- API Calling
-
API
- Protected Domain Name Management
-
HTTP Protection Policy Management
- This API is used to query the protection policy list.
- This API is used to create a protection policy.
- This API is used to query a protection policy.
- This API is used to update a protection policy.
- This API is used to delete a protection policy.
- This API is used to update domain names a policy applies to.
- This API is used to update a protection policy rule.
- EdgeSec HTTP Protection Rule Management - CC
- HTTP Protection Rule Management - Precise Protection
-
HTTP Protection Rule Management - IP Address Blacklist and Whitelist
- This API is used to query IP address blacklist and whitelist rules.
- This API is used to create an IP address blacklist or whitelist rule.
- This API is used to query an IP address blacklist or whitelist rule.
- This API is used to update an IP address blacklist or whitelist rule.
- This API is used to delete a blacklist or whitelist rule.
-
HTTP Protection Rule Management - Geographical Location
- This API is used to query the geolocation access control rules.
- This API is used to create a geolocation access control rule.
- This API is used to query a geolocation access control rule.
- This API is used to update a geolocation access control rule.
- This API is used to delete a geolocation access control rule.
-
HTTP Protection Rule Management - False Alarm Masking
- This API is used to query false alarm masking rules.
- This API is used to add a false alarm masking rule.
- This API is used to query a false alarm masking rule.
- This API is used to update a false alarm masking rule.
- This API is used to delete a false alarm masking rule.
- This API is used to reset a false alarm masking rule.
- HTTP Protection Rule Management - Attack Penalty
- IP Address Group Management
- Security Overview
- Reference Table Management
- DDoS Statistics
- HTTP Statistics
- DDoS Attack Logs
-
Appendix
- Status Code
- Error Codes
-
Troubleshooting
- EdgeSec.00000005 Invalid Parameter
- EdgeSec.00000013 Concurrent Modification Exception
- EdgeSec.00000014 Only Default Enterprise Project Supported (Not support operation in this enterprise project)
- EdgeSec.00000015 Write Operation Not Supported When All Enterprise Projects Are Selected (All enterprise projects do not support the write operation)
- EdgeSec.00000018 Migration of Resources to Non-Default Enterprise Project Not Supported (This version only supports default enterprise project)
- EdgeSec.00000019 Frozen Resources Cannot Be Migrated to or from an Enterprise Project (frozen cannot create eps tag)
- EdgeSec.00000023 Operation Not Supported by the Current Specifications
- EdgeSec.00000025 Invalid Block Time (Invalid block time)
- EdgeSec.00000026 Invalid Whitelist Rule Type (Invalid rule type)
- EdgeSec.00000027 Invalid CC Rule Condition Length (Invalid cc condition length value)
- EdgeSec.00010001 Invalid IAM Service Project (Failed to get IAM projects)
- EdgeSec.00010005 Insufficient WAF Policy Rule Quota
- EdgeSec.00010006 Blacklist and Whitelist Rules of Edge WAF Exceed the Quota
- EdgeSec.00010007 Insufficient IP Address Group Quota of Edge WAF
- EdgeSec.00010008 Insufficient Edge WAF Certificate Quota
- EdgeSec.00030001 Invalid DDoS Overview Parameters (Illegal Elasticsearch Request)
- EdgeSec.00030003 DDoS Overview Query Type Exception (Statistic Type Error)
- EdgeSec.00030002 DDoS Overview Query Type Exception (Search Error)
- EdgeSec.00040007 No Permission To Operate
- EdgeSec.00040013 Insufficient Top-Level Domain Name Quota
- EdgeSec.00040014 Expansion Resource Quota Has Been Used
- WAF.00022002 Resource Already Exists (Domain Already Exists)
- WAF.00014002 Resource Already Exists
- common.01010003 No Purchase Permission
- Obtaining a Project ID
- SDK Reference
-
FAQs
- About the Product
-
About Functions
- How Does EdgeSec Detect SQL Injection, XSS, and PHP Injection Attacks?
- How Do I Obtain the Real IP Address of a Visitor in EdgeSec?
- How Does EdgeSec Block Requests?
- Do I Need to Enable All Ports When Configuring an EdgeSec Whitelist in a Security Group?
- Why Do Cookies Contain the HWEdgeSecSESID or HWEdgeSecSESTIME field?
- Does Edge Security Support Alarm Notifications for Attacks?
- Regions and AZs
- General Reference
Copied.
Billing Items
Billing Description
When using EdgeSec, you will be billed for the service edition (mandatory), requests or service traffic protected (mandatory), and expansion package (optional) you use. For details, see EdgeSec billing items.
Billing Item |
Description |
Billing Mode |
Formula |
|
---|---|---|---|---|
Edition (mandatory) |
You are charged by service edition (enterprise edition). |
Yearly/Monthly billing |
Service edition x Required duration |
|
Service traffic |
Security acceleration traffic |
You are billed by the traffic used per hour. You can also buy traffic packages to deduct traffic used. You are billed at tiered traffic prices. The billing cycle is one calendar month. The actual network traffic is 7% to 15% higher than the traffic measured at the application layer as there is certain amount of traffic generated by TCP/IP packet headers and TCP retransmission. Therefore, the billable traffic will be typically 10% higher than the statistics displayed on the console. |
Pay-per-use billing |
Actual traffic (GB) x Tiered traffic price
There are five tiers:
|
Service requests |
Number of HTTP/HTTPS requests that are protected by EdgeSec |
Pay-per-use billing |
Actual number of requests (per 10,000 requests) x Unit price |
|
Rule expansion package (optional) |
Billed based on how many packages you purchased |
Yearly/Monthly billing |
Unit price of a package x Required duration |
|
Domain expansion package (optional) |
Billed based on how many packages you purchased |
Yearly/Monthly billing |
Unit price of a package x Required duration |
|
Dynamic acceleration service request |
Number of CDN dynamic acceleration requests. |
Pay-per-use billing |
Actual number of requests (per 10,000 requests) x Unit price Bills are settled on a monthly basis. |
Billing Rules
- If a domain name is added to Edge Security Acceleration (ESA), the incremental service fees (including acceleration and security functions) generated by the domain name are charged by ESA only. CDN stops the billing for the domain name.
- If a domain name is removed from ESA, the domain name is still charged by ESA before 24:00 on the day it is deleted and then charged by CDN after that time.
- For pay-per-use ESA incremental services (billed by traffic and number of requests), the minimum billing cycle is 5 minutes. For example, if a domain name is added to ESA at 10:03, the domain name is charged by CDN before 10:05, and the domain name is charged by ESA from 10:05 to 24:00.
- The traffic volume displayed on the statistical analysis page is calculated based on application-layer logs. The actually network traffic (TCP/IP packet header traffic and TCP retransmission traffic) is 7% to 15% higher than the traffic volume displayed. So, you will find the billed traffic is 10% higher than the statistical traffic.
Impacts of Expiration
EdgeSec resource lifecycle shows the statuses a yearly/monthly EdgeSec can go through throughout its lifecycle. After a service is purchased, it enters the valid period and runs normally during this period. If the service is not renewed after it expires, before being deleted, it first enters a grace period and then a retention period.
Expiration Reminder
From the 7th day before a yearly/monthly EdgeSec subscription expires, the system will send an expiration reminder to the creator of the account by email, SMS, and internal message.
Impacts of Expiration
If your yearly/monthly EdgeSec resource expires and is not renewed, the resource enters the grace periods. During the grace period, you can use the service.
If you do not renew the yearly/monthly EdgeSec resource within the grace period, the resource enters the retention period and the resource status changes to Frozen. You cannot perform any operation on the yearly/monthly resource during the retention period.
If the yearly/monthly EdgeSec resource is not renewed by the time the retention period ends, the resource will be released and data cannot be restored.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot