Regions
What is regional, what is global, and the regions that exist.
Available regions
| Region | Location |
|---|---|
eu-west-2 | London |
eu-west-2 is the only region today.
Regional and global
Game servers, autoscaling groups, schematics, sandboxes, Agones Autopilot fleets, logs and player sessions, networks and firewall rules, secrets and container repositories. Anything that runs, or is kept, somewhere.
Your account, projects, members and access, API keys and service accounts, billing, quotas, activity and support cases. Anything about you rather than about something running.
A regional resource says so in its name:
projects/{project}/locations/{location}/gameServers/{game_server}Every call goes to one endpoint, api.plany.cloud:443, whatever region it is about.
The region is in the resource name or the parent you send, so one client can work
with several regions at once.
Regions are independent of one another: a problem in one does not take the others with it.
Choosing one
There is no default region to configure on an account. The console has a region
selector, and a link that carries a resource name works whatever region the reader
has selected — the name decides, not the selector. The CLI takes one from its
configuration (plany config set region eu-west-2) or --region; the Terraform
provider from its region setting or PLANY_REGION.
What being regional means in practice
| Thing | Consequence |
|---|---|
| Quota | Most limits are per project and region. A project can hold its full instance limit in each region it uses. |
| Networks | Workloads reach each other privately within a region, not across two. |
| Schematics | Belong to the region they were captured in. |
| Secrets | Belong to one region. A workload reads secrets from its own region. |
| Container images | A repository lives in one region, at <region>.plany.cr. |
| Builds | Not regional — they belong to the account, so one upload serves every project in every region. |