- 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.
Cost Management
As you migrate more of your services to the cloud, managing cloud costs becomes more important. How to manage costs and reduce service loads when using EdgeSec is also our concerns. The following describes how to manage costs in terms of cost composition, allocation, analysis, and optimization. Optimizing costs can help you maximize return on investment.
Cost Composition
When using EdgeSec, you will use some resources, which depend on billing items of EdgeSec you are using. For details, see Billing Items.
Cost Allocation
A good cost accountability system is a prerequisite for cost management. It ensures that departments, business teams, and owners are accountable for their respective cloud costs. An enterprise can allocate cloud costs to different teams or projects so as to have a clear picture of their respective costs.
We provide multiple tools for you to optimize cost allocation in Cost Center.
- Allocate costs by linked account.
The enterprise master account can manage costs by grouping the costs of its member accounts by linked account. For details, see Viewing Costs by Linked Account.
- Allocate costs by cost category.
You can use Cost Categories in Cost Center to split shared costs. Shared costs are the costs of resources (compute, network, storage, or resource packages) shared across multiple departments or the costs that cannot be directly split by cost tag or enterprise project. These costs are not directly attributable to a singular owner, and they cannot be categorized into a singular cost type. In this case, you can define cost splitting rules to fairly allocate these costs among teams or business units. For details, see Viewing Cost By Cost Category.
Cost Analysis
To precisely control and optimize your costs, you need a clear understanding of what parts of your enterprise incurred different costs. Cost Center visualizes original costs and amortized costs in various dimensions and through filters so that you can analyze service usage costs, trends, and factors from a variety of perspectives and scopes.
You can also use Cost Anomaly Detection in Cost Center to detect unexpected expenses in a timely manner. In this way, costs can be monitored, analyzed, and traced.
For details, see Performing Cost Analysis to Explore Costs and Usage and Enabling Cost Anomaly Detection to Identify Anomalies.
Cost Optimization
- Cost control
You can create different types of budgets on the Budgets page of Cost Center to track your costs against the budgeted amount you specified and send alerts to the recipients you configured if the thresholds you defined are reached. You can also create budget reports and specify recipients to receive budget alerts if any at a frequency you configured.
For example, an enterprise needs to create a cost budget for EdgeSec. The monthly budget is $2,000 USD. The system should send an alarm when the forecast amount is greater than 80% of the budget amount. You can refer to the following budget information.
Figure 1 Basic budget informationFigure 2 Defining the budget scopeFigure 3 Setting a budget alertFor details, see Enabling Forecasting and Creating Budgets to Track Cost and Usage.
- Resource optimization
Cost Center analyzes your historical CPU and other resource usage to identify idle EdgeSec resources and generate resource rightsizing recommendations. These rightsizing opportunities are places where you can reduce costs. You can also identify resources with high costs based on the analysis results in the cost analysis phase and use Cloud Eye to monitor resource usage. By doing this, you can determine the causes of high costs and take optimization measures accordingly.
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