Google Cloud’s November 3, 2026 release notes add Mumbai (asia-south1) and Moncks Corner, South Carolina (us-east1), among seven regions for Application Design Center. If your team is choosing one of those locations, write down two decisions: where the application is managed and where its underlying resources should run.
Google Cloud’s November 3 release notes
The space is the management location
Google’s space documentation describes regional spaces in which teams create templates, components and application drafts. After deployment, the application remains managed from its originating space. The underlying resources can be provisioned in supported regions, so the location of the space alone does not tell you where each resource runs.
Google Cloud: how spaces and deployment locations relate
Read the two fields separately
The gcloud reference illustrates an application created with location us-central1 and deployment-region us-east1. In that example, the first value identifies the location of the application record and the second sets the deployment region. The example explains the distinction; it does not certify a particular template’s compatibility.
Google Cloud CLI reference and example
Suppose a fictional team creates its draft in a Mumbai space and intends to deploy a regional workload in South Carolina. Record Mumbai as the management location, South Carolina as the intended deployment region, and the intended deployment project on its own line. Before proceeding, check each component’s regional support, the template’s settings and your organization’s location restrictions. This is a planning example, not a tested deployment.
Verify what was actually provisioned
After an authorized deployment, compare the intended region with the location shown for each actual resource. Treat a global component as global rather than assigning it the same regional label as a nearby service. Record any mismatch or unresolved item before treating the inventory as complete. A newly available management region is useful, but it does not relocate an existing workload or establish where every category of data is stored.