Discuss a cloud requirement

APAC architecture

APAC architecture here is region selection, residency constraints and the provider primitives that apply when users or regulated data sit in Asia-Pacific, including Alibaba Cloud.

Who this topic is for

Architects whose users or data must stay in APAC, or whose current diagrams still start from a US workshop region.

Problems these pages cover

  • A US default region became production without measurement.
  • Residency rules were assumed to be satisfied by picking a city name.
  • Alibaba Cloud was designed using AWS names.

Recommended reading order

  1. Choosing a primary cloud region for APAC workloads
  2. Alibaba Cloud architecture for APAC
  3. Alibaba Cloud
  4. Building Secure Alibaba Cloud ACK Platforms
  5. AWS, Azure, Google Cloud and Alibaba Cloud in APAC

Guides in this topic

Ankit Mehta

Choosing a Primary Cloud Region for APAC Workloads

A US workshop account often lands in us-east-1 or eastus because the lab image and quota already exist there. Production users and regulated data in Singapore, Jakarta, Tokyo, Sydney or Hong Kong then inherit that default. Confirm the current regional service list for the provider you run before you treat a city name as available.

10 min read

Related runbooks

Consulting

Scoped review for this topic: Cloud architecture consulting in APAC.