Cross-AZ data transfer billing (OceanBase Cloud on AWS)

To better align with the billing practices of major public cloud providers and to enhance transparency between resource usage and associated costs, OceanBase Cloud on AWS (including both self-operated and AWS Marketplace offerings—please refer to your console for the exact product model you are using) will introduce a new, dedicated billing line item to reflect data transfer usage within the same AWS Region but across different Availability Zones (AZs).

General background on cloud provider data transfer charges

Public cloud providers such as AWS, Google Cloud, and Microsoft Azure typically charge for data movement, whether within their infrastructure or egressing to the internet, on a consumption basis (measured in GB or GiB, per each provider's billing granularity).

In the course of using OceanBase Cloud, the following scenarios may generate measurable and billable data transfer traffic:

• When your applications access OceanBase Cloud databases via public internet, Direct Connect, or VPC endpoints (subject to the cloud provider's network pricing policies);
• When data flows between load balancers/access layers and OceanBase cluster components (e.g., via database proxy);
• When data is transferred between components of the same cluster across different AZs within the same Region (e.g., cross-AZ queries or replication links);
• When performing backup and restore operations (which may involve intra- or inter-Region data movement);
• When using data migration or synchronization features to move data into or out of the cluster.

Rationale for this change (cross-AZ data transfer within the same AWS Region)

On AWS, data transfer across Availability Zones within the same Region is a significant component of total operational cost. According to AWS's published pricing, this type of traffic is billed on a per-volume basis. Industry-leading cloud database services (e.g., Amazon Aurora) already expose cross-AZ data transfer as a separate, transparent line item to help customers understand and optimize their architectures.

For reference (not a commitment by OceanBase; please consult official vendor websites for the latest details):

• AWS On-Demand EC2 Pricing (includes data transfer)
• Amazon Aurora Pricing (includes cross-AZ replication costs)

Historically, OceanBase Cloud on AWS has absorbed the cost of intra-Region cross-AZ data transfer in certain scenarios. However, with the growing adoption of high-concurrency and distributed deployment patterns, this cost has become increasingly material to sustainable operations.

OceanBase Cloud is introducing this dedicated billing item to achieve:

• Greater cost transparency;
• Consistency with industry-standard cloud database offerings;
• Improved alignment between incurred costs and revenue recognition for accurate financial reconciliation.

Billing item details and presentation

• Billing line item name: Cross-AZ Data Transfer

• Metering and pricing model: Billed per GiB of data transferred, using a cost-pass-through model, i.e., no markup above AWS's official list price for regional cross-AZ data transfer.

• Unit price (list price equivalent): 0.01 USD per GiB

  This rate is consistent with AWS's standard pricing for intra-Region cross-AZ data transfer and applies globally across all AWS Regions where OceanBase Cloud is available.

  Note

  Local Zones are not supported by OceanBase Cloud and will not trigger this charge.

• Aggregation scope: To simplify cost attribution across internal components, OceanBase Cloud will aggregate all cross-AZ data transfer within a single cluster and present it as one unified line item. This includes, but is not limited to:

  • Application traffic to database proxy;
  • Database proxy accessing database nodes across AZs;
  • Intra-cluster data replication across AZs;
  • Data migration/synchronization operations involving cross-AZ movement;
  • Backup and restore activities generating cross-AZ traffic.

Effective date

This billing item will take effect and begin charging at 00:00:00 (UTC+8) on April 1, 2026.

Recommended actions

• Review your replica topology and cross-AZ access patterns in light of your business RPO/RTO and high-availability requirements, balancing resilience against network cost.
• Monitor the Cross-AZ Data Transfer usage trends in your OceanBase Cloud console and billing statements, and correlate them with application traffic peaks or architectural changes.

If you have questions, reach out to your account manager or contact us through official support channels.