Cloud Firewall
Cloud Firewall
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Creating a User Group and Granting Permissions
- Checking the Dashboard
- Purchasing and Changing the Specifications of CFW
- Enabling Internet Border Traffic Protection
- Enabling VPC Border Traffic Protection
-
Configuring Access Control Policies to Control Traffic
- Access Control Policy Overview
- Configuring Protection Rules to Block or Allow Traffic
- Adding Blacklist or Whitelist Items to Block or Allow Traffic
- Viewing Protection Information Using the Policy Assistant
- Managing Access Control Policies
- Managing IP Address Groups
- Domain Name Management
- Service Group Management
- Attack Defense
- Viewing Traffic Statistics
- Viewing CFW Protection Logs
- System Management
- Viewing Audit Logs
- Viewing Monitoring Metrics
-
Best Practices
- CFW Best Practice Summary
- Purchasing and Querying CFW via API
- Migrating Security Policies to CFW in Batches
- Configuration Suggestions for Using CFW with WAF, Advanced Anti-DDoS, and CDN
- Allowing Internet Traffic Only to a Specified Port
- Allowing Outbound Traffic from Cloud Resources Only to a Specified Domain Name
- Using CFW to Defend Against Network Attacks
-
API Reference
- Before You Start
- API Overview
- API Calling
-
API
- Domain Name Management
- VPC Protection
- Rule Hit Count
- IPS Switch Management
- East-west Protection
- ACL Rule Management
- Blacklist and Whitelist Management
- Log Query Management
- Protection Mode Management
- Cloud Firewall Information Management
- Service Group Management
- Service Group Member Management
- EIP Management
- Address Group Member Management
- Address Group Management
- Appendix
- Change History
- SDK Reference
-
FAQs
-
About the Product
- Does CFW Support Off-Cloud Servers?
- Can CFW Be Shared Across Accounts?
- What Are the Differences Between CFW and WAF?
- What Are the Differences Between CFW, Security Groups, and Network ACLs?
- How Does CFW Control Access?
- What Are the Priorities of the Protection Settings in CFW?
- Can WAF and CFW Be Deployed Together?
- How Long Are CFW Logs Stored by Default?
- Regions and AZs
- Troubleshooting
-
Network Traffic
- How Do I Calculate the Number of Protected VPCs and the Peak Protection Traffic at the VPC Border?
- How Does CFW Collect Traffic Statistics?
- What Is the Protection Bandwidth Provided by CFW?
- What Do I Do If My Service Traffic Exceeds the Protection Bandwidth?
- What Are the Differences Between the Data Displayed in Traffic Trend Module and the Traffic Analysis Page?
- How Do I Verify the Validity of an Outbound HTTP/HTTPS Domain Protection Rule?
- Billing
-
About the Product
- Videos
On this page
What Are Regions and AZs?
Updated on 2022-10-31 GMT+08:00
Concepts
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
- Regions are divided from the dimensions of geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region. Regions are classified as universal regions and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides services of the same type only or for specific tenants.
- An AZ contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to allow you to build cross-AZ high-availability systems.
Selecting a Region
If you or your users are in Europe, select the EU-Dublin region.
Selecting an AZ
When determining whether to deploy resources in the same AZ, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs in the same region.
- For low network latency, deploy resources in the same AZ.
Parent topic: Regions and AZs
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.