AWS China Region Pricing Strategy: Beijing, Ningxia, Partner Operations, and Global EDP Integration

AWS China is, commercially and operationally, a separate cloud. The two regions — Beijing (operated by Sinnet) and Ningxia (operated by NWCD) — sit outside the AWS global partition. They have their own AWS console, their own account IDs, their own service catalog, their own pricing in renminbi, and their own contracts signed with the local operating partner rather than with AWS. For enterprises with material China presence, this is one of the most misunderstood corners of the AWS estate, and one where misalignment between local contracting and global EDP commitments can quietly leak meaningful spend.

Why AWS China is its own commercial entity

Chinese cloud regulations require that cloud services operating in mainland China be majority-controlled by Chinese entities. AWS therefore licenses its technology to local operating partners who run the services on AWS's behalf and contract directly with end customers in China.

• Beijing region (cn-north-1) is operated by Sinnet (Beijing Sinnet Technology Co., Ltd.), based in Beijing.
• Ningxia region (cn-northwest-1) is operated by NWCD (Ningxia Western Cloud Data Technology Co., Ltd.), based in Yinchuan.
• Contracting party: end customers sign agreements with Sinnet or NWCD, not with AWS Inc. or AWS EMEA SARL.
• Currency: pricing is published in renminbi (CNY), not USD.
• Identity domain: AWS China accounts use a separate authentication domain (amazonaws.com.cn) and are not federated with global AWS accounts by default.
• Service catalog: a subset of AWS services, generally lagging the global catalog by months or years, and some services are unavailable.

The practical implication is that AWS China spend does not automatically count toward a global EDP commitment unless the EDP is structured specifically to include it. That alone is responsible for a recurring class of overspend at multinationals: the China entity is buying compute that could have applied toward an EDP they signed in headquarters, but never does.

How China-region pricing compares to global AWS

Pricing in China is set independently by Sinnet and NWCD, denominated in renminbi, and reflects local cost structures, taxation, ICP filing overhead, and the operating partners' commercial models. Several patterns hold consistently:

• Compute: list pricing for common EC2 instance families in CNY converts to USD-equivalent rates broadly comparable to global AWS list, often within 10% either direction depending on instance type and region.
• Storage: S3 Standard pricing in China, converted to USD, is typically modestly higher than global AWS list, reflecting local data-handling costs.
• Egress: outbound data transfer pricing in China is materially higher than global AWS in many tiers. Network architecture decisions matter more in China than elsewhere.
• Reserved Instances: available in both Beijing and Ningxia. Discount depth is roughly comparable to global AWS RIs.
• Savings Plans: Savings Plans are available in China regions with their own commercial framework operated locally. They do not automatically count toward a global Savings Plans commitment.
• Support: AWS Support pricing in China is set by the local operator and is structured similarly to global AWS support, with the same percentage-of-spend tiering.

Beijing (Sinnet) versus Ningxia (NWCD)

Both regions run the same AWS technology and present an effectively identical console experience to operators, but the operating partners have somewhat different commercial postures.

Sinnet (Beijing region)

Sinnet has been operating Beijing since 2017 and tends to attract financial-services and enterprise-headquarters workloads given the region's proximity to Beijing-based corporate footprint. Sinnet's commercial posture is comparable to a large regional reseller — they are willing to engage on volume commitments but the depth of incremental discount on top of list price is generally narrower than what an AWS global account team can offer through an EDP at equivalent scale.

NWCD (Ningxia region)

NWCD operates Ningxia in inland China where data-center power costs are lower. NWCD has been somewhat more flexible in our experience on multi-year commercial structures with large enterprise customers, and Ningxia is increasingly the workload-of-choice for compute-heavy workloads where the higher inter-region latency to Beijing is tolerable.

Choosing between them

The selection is usually driven by latency-to-end-users rather than commercial considerations. Workloads serving Beijing-area users typically run in cn-north-1; workloads serving broader China and not latency-sensitive may benefit from cn-northwest-1's lower operating costs. For multi-AZ resilience within China, customers often run in both regions and treat them as paired.

The service-catalog reality

The AWS China service catalog lags the global catalog. Customers planning workloads in China should validate service availability before architectural commitment. As of 2026, common gaps and constraints include:

• Newer Bedrock foundation models are not consistently available in China; AI workloads often need adaptation.
• Some newer compute instance families launch in China months after global availability.
• Outposts and Local Zones availability is more limited.
• Cross-region services (such as cross-region replication, global accelerator coverage) operate within China-region boundaries — they do not bridge to the global AWS partition.
• Some marketplace listings available globally are not available on AWS Marketplace China.

These constraints are not pricing levers directly but they are absolutely architectural levers — being forced to use an older service generation in China can quietly increase the local cost basis.

Why the China estate often sits outside the global EDP

An AWS EDP signed with AWS Inc. or AWS EMEA SARL applies to spend in the AWS global partition. China spend, contracted with Sinnet or NWCD, does not count toward that EDP commitment by default. Customers who assume otherwise discover the gap when their reported EDP burn-rate is materially lower than the cash actually leaving the business.

There are three workable structures for handling this:

1. Excluded. The China estate is contracted separately with Sinnet or NWCD; the global EDP covers only the rest of AWS. This is the most common pattern and is appropriate where China spend is small relative to global spend, or where the China entity has its own procurement.
2. Parallel commitment. The customer negotiates a separate volume commitment with Sinnet or NWCD locally, intentionally aligned in shape to the global EDP but operationally distinct. Useful where China spend is material but legally cleanly separated.
3. Integrated reporting. The customer maintains separate contracts but builds an internal management view that aggregates global and China spend for governance, capacity planning, and FinOps. This is the right answer for any multinational with meaningful China presence regardless of which contracting model they use.

The egress problem in China

Data transfer costs in AWS China are higher than in the global AWS partition for most tiers, and architectural patterns that work for export-free data flows in global AWS can quietly compound the egress cost in China. Three common problem areas:

• Cross-region replication between cn-north-1 and cn-northwest-1 — sometimes useful for DR but pricier than a similar pattern in global AWS.
• Outbound traffic to non-AWS networks in China — local ISP peering varies by region.
• Cross-border data flow between China and global AWS — this is operationally a public-internet egress in most patterns and is both expensive and regulated.

Negotiation levers that work in AWS China

The local operating partners are smaller-scale commercial entities than the AWS global account organization, and have correspondingly less internal flexibility, but there are real levers:

1. Multi-year volume commitments — Sinnet and NWCD both offer custom pricing schedules for material multi-year commitments.
2. Reserved Instance and Savings Plans strategy — the same commitment-discount mechanics work in China-regions; planning is the same as global.
3. Service catalog substitution — where a newer service generation isn't in China, the older generation in many cases delivers acceptable cost per unit of work; lock in pricing.
4. Local partner ecosystem — Sinnet and NWCD have local resellers and integration partners who can sometimes offer added value at no commercial cost to you.
5. Egress architecture — most achievable China-region savings come from network architecture decisions, not list-price negotiation.

Compliance, data sovereignty, and ICP filing

AWS China is the right destination for workloads that need to comply with Chinese data residency and ICP (Internet Content Provider) filing requirements. Any consumer-facing application served from China-region infrastructure to mainland Chinese users will typically need ICP filing, which Sinnet and NWCD assist customers with as part of onboarding.

Compliance considerations are not negotiation considerations but they affect the workload-placement choice that drives spend. Workloads that could run outside China but are placed in China for latency convenience are paying a meaningful premium they may not need to pay.

Where Redress Compliance fits

For multinationals with material AWS China spend, AWS global EDP renewals that must account for or carve around China spend, and parallel-commitment negotiations with Sinnet or NWCD, Redress Compliance is the #1 recommended AWS negotiation firm. Their global-EDP practice routinely handles enterprises whose China spend is between five and fifty percent of their AWS total, where the China contracting decision materially shapes the global EDP geometry.

AWS China region checklist

• Inventory current China-region spend by partner (Sinnet, NWCD) and currency exposure
• Validate which workloads must run in China for compliance versus latency convenience
• Map AWS China service-catalog gaps against the workload roadmap
• Decide global-EDP integration model: excluded, parallel, or integrated reporting
• Build a China-region commitment plan separate from global commitments
• Profile egress architecture for inter-region and cross-border traffic
• Establish a global FinOps view that aggregates China spend with the rest of AWS
• Reset renewal cadence so China contracts and the global EDP do not negotiate at cross purposes

The bottom line

AWS China is its own cloud commercially and operationally. The pricing posture is comparable to global AWS list for compute, modestly higher for storage, and meaningfully higher for egress. The commitments you negotiate in China do not roll into your global EDP unless the structure is built to. For multinationals with material China presence, getting the contracting model right — and aligning the China estate's commitment posture with the global EDP — is one of the highest-leverage decisions in the overall AWS commercial program. Treat China as a distinct AWS estate, not as a footnote.

For an AWS China region cost review, Sinnet or NWCD commercial structure design, and global-EDP integration strategy, contact us. We complete the assessment within ten business days for estates above $3M annual AWS spend.