Essential-HighAvailability-changed

tidb-cloud/architecture-concepts.md

@@ -53,15 +53,9 @@ For applications experiencing growing workloads and needing scalability in real
 
 - **Enhanced capabilities**: includes all capabilities of the Starter plan, along with the capacity to handle larger and more complex workloads, as well as advanced security features.
 - **Automatic scaling**: automatically adjusts storage and computing resources to efficiently meet changing workload demands.
-- **High availability**: built-in fault tolerance and redundancy ensure your applications remain available and resilient, even during infrastructure failures.
 - **Predictable pricing**: billed based on storage and Request Capacity Units (RCUs) of the compute resources, offering transparent, usage-based pricing that scales with your needs, so you only pay for what you use without surprises.
 
-{{{ .essential }}} offers two types of high availability to address varying operational requirements.
-
-- Zonal High Availability: places all components within the same availability zone, which results in lower network latency.
-- Regional High Availability: distributes nodes across multiple availability zones, providing maximum infrastructure isolation and redundancy.
-
-For more information, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md).
+{{{ .essential }}} offers Zonal High Availability: places all components within the same availability zone, which results in lower network latency. For more information, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md).
 
 ## {{{ .premium }}}
 

tidb-cloud/features.md

@@ -253,7 +253,7 @@ This document lists the feature support status for different TiDB Cloud plans, i
     <td rowspan="1" style="background-color: white;">High availability</td>
     <td>Cross-AZ failover</td>
     <td style="text-align:center; font-size: 14px;">❌</td>
-    <td style="text-align:center;">✅</td>
+    <td style="text-align:center;">❌</td>
     <td style="text-align:center;">✅</td>
     <td style="text-align:center;">✅</td>
   </tr>

tidb-cloud/serverless-high-availability.md

@@ -22,7 +22,7 @@ TiDB Cloud extends these capabilities with zonal high availability and regional
 >
 > - For {{{ .starter }}} instances, only zonal high availability is enabled, and it is not configurable.
 > - For {{{ .premium }}} instances, only regional high availability is enabled and is not configurable.
-> - For {{{ .essential }}} instances hosted in the AWS Tokyo (ap-northeast-1) region or any Alibaba Cloud region, regional high availability is enabled by default. You can change it to zonal high availability as needed during {{{ .essential }}} instance creation. For {{{ .essential }}} instances hosted in other regions, only zonal high availability is enabled, and it is not configurable.
+> - For {{{ .essential }}} instances, only zonal high availability is enabled, and it is not configurable.
 
 - **Zonal high availability**: This option places all nodes within a single availability zone, reducing network latency. It ensures high availability without requiring application-level redundancy across zones, making it suitable for applications that prioritize low latency within a single zone. For more information, see [Zonal high availability architecture](#zonal-high-availability-architecture).
 
@@ -86,7 +86,7 @@ The gateway and computing layers are stateless, so failover involves restarting
 
 ## Regional high availability architecture
 
-When you create a {{{ .essential }}} or {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximizing availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation.
+When you create a {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximizing availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation.
 
 > **Note:**
 >

tidb-cloud/serverless-private-link-connection-to-aws-rds.md

@@ -48,7 +48,7 @@ The Amazon RDS instance must meet the following requirements:
 
 > **Note**
 >
-> To connect to a cross-region RDS instance, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md).
+> Private Link currently does not support cross-region connectivity. For cross-region connections, it is recommended to use VPC peering to establish a link (TiDB Cloud Premium only feature).
 
 ## Step 2. Expose the Amazon RDS instance as an endpoint service