Regions

Devices connect to a FlexGalaxy.AI region: a platform-owned operating environment with its own endpoints, not an AWS location. Each region has a separate device-connection endpoint (for example things.flexgalaxy.ai and things.ap-northeast-2.flexgalaxy.ai), and the provisioning response for a device names the endpoint of the region it was provisioned into.

Every Thing has one home region. It is fixed when the device is provisioned and governs its connections, attributes, telemetry and operations. It is not changed by:

• where the device physically is (a traveling device keeps connecting to its home region),

• which region you selected in the console (the selector chooses where you operate, it does not move devices),

• ownership transfer, reset, or re-provisioning.

Provisioning into the wrong region is refused, not redirected: the request fails with 409 and the error code DDI-1-409-REGION-MISMATCH, whose body names the home region and the correct device endpoint to use. Retrying against the home endpoint is the fix; there is no automatic redirect.

Moving a Thing to another region is an explicit, audited platform-admin workflow — never a side effect, and not currently self-service. Until that workflow is available, treat the home region as permanent and choose the region deliberately at provisioning time.

Regions live inside partitions (Global and, separately, China). Thing and Model IDs are globally unique, but uniqueness is not access: nothing crosses a partition boundary, and region selection cannot point at another partition.

ThingMake administration — manufacturers, device models, Registrars and the serial namespace — is managed once per partition, while provisioning execution and device endpoints are regional. A Registrar can be enabled for several regions; enablement is explicit, and the provisioning destination is chosen explicitly (or by the Registrar’s configured default) rather than inferred.