Globally distributed service
Our avatar service runs in multiple regions. You can choose the region that’s closest to your infrastructure to minimize latency.Available regions
Use these region names when selecting a deployment:- ap-northeast
- us-west
Console API hosts
When a doc example uses<console-api-host>, substitute the host for your region:
| Region | <console-api-host> |
|---|---|
ap-northeast | console.ap-northeast.spatialwalk.cloud |
us-west | console.us-west.spatialwalk.cloud |
Console and Ingress endpoint URLs
When a doc example uses console endpoint url or ingress endpoint url, substitute the URL for your region:| Region | Console Endpoint URL | Ingress Endpoint URL (v2) |
|---|---|---|
ap-northeast | https://console.ap-northeast.spatialwalk.cloud/v1/console | wss://api.ap-northeast.spatialwalk.cloud/v2/driveningress |
us-west | https://console.us-west.spatialwalk.cloud/v1/console | wss://api.us-west.spatialwalk.cloud/v2/driveningress |
Cross-region portability
The following identifiers/credentials are not region-specific and can be used across regions:- App ID
- API Key
- Avatar ID
- Session Token (generated by the console API)
High availability with regional fallback
Services in different regions run on separate infrastructure, so you can improve availability by implementing fallback:- Primary + backup: if requests to the primary region fail, retry against another region.
- Data sync: since the identifiers/credentials mentioned above are portable, you can keep using them when failing over to another region.