AWS China: Speed, Compliance & Better Alternatives
A guide to Amazon Web Services in China—Beijing & Ningxia regions, account setup, ICP compliance, performance pitfalls, and how a 21YunBox overlay keeps global AWS builds fast and legal inside the Great Firewall.
Does Amazon Web Services work in China?
AWS in mainland China is a separate cloud, not a region of your existing one. The Beijing and Ningxia Regions are operated by Chinese partners — Sinnet and NWCD — under separate customer agreements, they are isolated from all other AWS Regions and not connected to the AWS global backbone, and they require a distinct set of AWS China credentials: your existing AWS account cannot reach them. So "we're on AWS" does not carry over. Moving there is a new deployment in a new account under a new contract, and — like any in-country delivery — it needs an ICP filing, which is why the fast path and the filed path are the same path. Measured fact: from a probe inside mainland China (Alibaba Cloudcn-zhangjiakou), three runs, 2026-08-27, aws.amazon.com completed only 1 of 3 attempts, at a median 7.8s load and 5.4s largest-contentful-paint. Two third-party hosts it requests never responded at all. Struggling with AWS China Performance? Get a Free Site Audit.
Our 21YunBox Optimizer overlays your current AWS stack to deliver sub-50 ms speeds and full ICP compliance—no migrations, no extra DevOps.
Book My AuditKeep building on AWS; we’ll handle China.
What Amazon Web Services (AWS)'s documentation says, and what we measured from inside China
| Fact | Primary source |
|---|---|
| The China Regions are operated by Chinese partners under separate agreements: AWS China (Beijing) is operated by Sinnet and AWS China (Ningxia) by NWCD, and customers "enter into customer agreements with Sinnet and NWCD, rather than with AWS." | Amazon Web Services in China — FAQs |
| Credentials do not carry across: customers "are required to create an AWS (China) Account… distinct and separate from other AWS global Accounts", and "customers with existing AWS credentials will not be able to access resources in the China Regions, and vice versa." | Amazon Web Services in China — FAQs |
| The China Regions "are isolated from all other AWS Regions" and "are not directly connected to AWS global backbone" — so a global CloudFront distribution or a global VPC does not extend into them. | Amazon Web Services in China |
| In-country delivery — the only arrangement that removes the cross-border round trip — carries the regulatory gate with it: "ICP filing applies only to servers located in the Chinese mainland", and the filing binds to the access provider, not only the domain. | Alibaba Cloud — ICP filing prerequisites |
| Amazon Web Services (AWS) was reachable and finished loading on all 3 attempts from a probe inside mainland China (Alibaba Cloud cn-zhangjiakou), measured 2026-08-28: median first byte 665ms, median paint 4,028ms. | 21YunBox — 280-site China delivery census, measured from inside mainland China |
| Measured again from a Beijing China Mobile residential broadband line on 2026-08-30, Amazon Web Services (AWS) completed 0 of 3 page loads — first byte in a median 743ms — against 3 of 3 from the datacenter probe. The datacenter result does not describe what a visitor on a consumer connection sees. | 21YunBox — paired measurement from a Beijing residential broadband line |
Sources verified by the 21YunBox China engineering team on 2026-08-28.
AWS China: What’s Different in 2025?
| Quick facts | Details |
|---|---|
| Regions | Beijing (cn-north-1) operated by Sinnet & Ningxia (cn-northwest-1) operated by NWCD |
| Separate account? | Yes. An AWS China account is mandatory; a global AWS account cannot access China regions |
| Must-have licenses | ICP Filing (all public sites) • PSB Filing (informational sites that collect no personal data) |
| Latency | Cross-border traffic averages 150–350 ms; packet loss/sporadic blocking common |
| Common fix | Keep your existing AWS build, add a 21YunBox Optimizer overlay to localize assets & handle compliance—no code rebuilds |
1 Why AWS Created Separate China Regions
Unlike standard global regions, AWS China operates under Chinese law. Services are physically segregated, billing is in RMB, and contracts are signed with local operators (Sinnet/NWCD) rather than Amazon US. This arrangement satisfies data-sovereignty rules but introduces extra paperwork, slower feature rollouts, and limited service parity.
2 Performance & Compliance Pitfalls
2.1 Speed
- Great Firewall latency – TLS handshakes and DNS lookups from China to non-Chinese IPs can add 200–500 ms.
- TCP resets – Cross-border API calls may drop unpredictably, hurting SPA/GraphQL apps.
- Content throttling – Large static assets (images, JS bundles, HLS video) often load under 1 Mbps without local caching.
2.2 Legal Requirements
| Requirement | When it applies | Typical paperwork |
|---|---|---|
| ICP Filing | Any publicly accessible domain | Local entity or trusted filing agent |
| PSB Filing | Informational sites collecting no user PII | Online PSB portal |
Skipping or misclassifying these steps risks domain blocking, license revocation, or server shutdowns.
3 Three Ways to Run AWS-Powered Workloads for China
| Option | Pros | Cons | Best for |
|---|---|---|---|
| 1. Global AWS only | Single build pipeline | High latency, firewall risk, non-compliant | Internal tools, staging |
| 2. Migrate to AWS China account | Native speeds, local IP | Separate account, fewer services, DevOps duplication | China-first products |
| 3. 21YunBox Optimizer overlay | Keep global AWS stack, < 50 ms TTFB in China, ICP/PSB handled for you | Small overlay fee | Existing global sites, limited China resources |
4 Implementation Checklist (2025)
- Domain strategy – Decide on a
.cnversus global TLD plus ICP filing. - Traffic split – Route China traffic to 21YunBox edge PoPs; keep the rest on CloudFront/global ALB.
- Data localization – Keep or shard onshore any user data that must stay in China.
- Monitoring – Use 21YunBox real-time uptime checks from 30+ mainland cities.
Next Steps
Get a free China site audit See exactly where latency, DNS misconfigurations, or compliance gaps cost you traffic. Start the audit →
Need deeper guidance? Explore our related guides:
Frequently Asked Questions
Does our existing AWS account work in China?
No. AWS China requires a separate AWS (China) account with distinct credentials, and AWS states plainly that existing credentials cannot access resources in the China Regions and vice versa. It is a different partition with a different contracting party.
Can we just add a China region to our current setup?
Not in the way that phrase implies. The China Regions are isolated from all other AWS Regions and are not connected to the AWS global backbone, so cross-region features you rely on globally do not span into them. Practically it is a second deployment to build, run and keep in sync — which is the operational cost people underestimate.
Does moving to AWS China solve our performance problem?
It genuinely does remove the border crossing, because delivery is then in-country. What it also does is trigger the ICP filing requirement and hand you a second stack to operate. Whether that trade is worth it depends on how much of your application really needs to live in China versus merely be reachable from it.
Do we need an ICP filing for AWS China?
Yes. Anything served from inside mainland China needs one, it is issued to a mainland legal entity, and it binds to the access provider — so the filing has to name the operator you are actually using.
