​
Overview

A cloud is a named group of regions treated as a single context. With one selected, a list call fans out across every region in the group and returns a combined result, so you see your whole estate in one view instead of switching regions one at a time.
Clouds are disabled in this release. Two independent switches hold it closed:
  • The console’s cloud controls are behind a hidden feature flag, so they do not appear in the interface.
  • The platform has an operational kill-switch, off by default. A request carrying the grouping header is refused outright:
Everything below describes intended behaviour so you can plan around it. Do not build on it yet.

​
How it works when enabled

A response from a fanned-out list carries an extra key:
Always read regionErrors. A non-empty array means the result is incomplete — some region did not answer — and treating a partial list as complete is how an instance gets missed in a count or a cleanup.The API is not consistent about this. Listing load balancer rules refuses to return a partial result and fails the request outright, because ownership could not be verified everywhere. Most other lists return what they have plus regionErrors. So absence of an error is not the same as a complete answer unless you checked the field.

​
Precedence

A cloud is a read convenience. Creating a resource still targets one region, because a resource lives in exactly one. Clouds change what a list spans, not where things are made.

​
The API

Documented under Clouds in the endpoint reference, and refused while the feature is off.
Membership requires an active account in each member region. Adding a region you have not activated fails — activate it first from Regions.

Regions

Region context, and why a bad header returns 403.

Regions and zones

The concepts behind regions.

Fabric

Actually connecting VPCs across regions.

Conventions

Response envelopes, including regionErrors.