# TiDB Cloud Provider Region
![left](./student-guide/diagram/TiDBCloudProviderRegion_aa_001_20220524.png)
------------------------------------------------------------
Cloud Provider AWS or GCP
VPC – Virtual Private Cloud – shows privacy and security are segmented  If you have used AWS to configure instances as a IAM user this will look familiarIf you are already familiar with provisioning resources in AWS or GPC

TiDB VPC (Virtual Private Cloud)
For each TiDB Cloud cluster, all TiDB nodes and auxiliary nodes, including TiDB Operator nodes, logging nodes, and so on, are deployed in an independent VPC.

TiDB Cloud Central Services
Central Services, including billing, alerts, meta storage, dashboard UI, are deployed independently. You can access the dashboard UI to operate the TiDB cluster via the internet.

Your VPC
You can connect to your TiDB cluster via a VPC peering connection. Refer to Set up VPC Peering Connection for details.


High Availability with Multi-AZ Deployments
TiDB uses the Raft consensus algorithm to ensure that data is highly available and safely replicated throughout storage in Raft Groups. Data is redundantly copied between storage nodes and placed in different availability zones to protect against machine or data center failures. With automatic failover, TiDB ensures that your service is always on.TiDB Cloud clusters consist of three major components: TiDB node, TiKV node, and TiFlash node. The highly availability implementation of each component is as follows:

    - TiDB  node
    TiDB is for computing only and does not store data. It is horizontally scalable. TiDB Cloud deploys TiDB nodes equally to different availability zones in a region. It is recommended that you configure at least two TiDB nodes in each TiDB Cloud cluster for high availability.

    - TiKV  node
    TiKV is for storing data. It is horizontally scalable and the number of nodes should be at least 1 set (3 nodes in 3 different availability zones). The data in TiKV of each TiDB Cloud cluster has 3 replicas, and each replica is stored in three different TiKV nodes which are distributed in three different availability zones.

    - TiFlash beta node
    As a columnar storage extension of TiKV, TiFlash beta is the key component that makes TiDB essentially a Hybrid Transactional/Analytical Processing (HTAP) database. In TiFlashbeta, the columnar replicas are asynchronously replicated according to the Raft Learner consensus algorithm. To save the cost of data transfer between TiFlash beta nodes, TiDB Cloud deploys all TiFlash beta nodes of one TiDB Cloud cluster in one availability zone in a region. It is recommended that you configure at least two TiFlash beta nodes in each TiDB Cloud cluster and create at least 2 replicas of the data for high availability in your production environment.

High Availability with Multi-AZ Deployments