Choosing the Right Cloud Region
After you choose the cloud provider, you choose the physical region of the datacenter where the event broker services are created. You can create event broker services in datacenters in any physical region, regardless
- Public Cluster and Dedicated Cluster deployments can choose from datacenters in any physical region around the world offered by the various cloud providers available in Solace Cloud. If you don't see a region for a cloud provider that you require, contact Solace.
- Customer-Controlled Cluster deployments have more flexibility in choosing deployment regions, as you own the infrastructure.
For more information, see Deployment Options for Solace Cloud and Deployment Architecture for Kubernetes.
You should consider the following before choosing the right region for creating your event broker service:
-
Physical Location—Choose a region that is physically close to the location where your microservices or client applications are running. If you are concerned with disaster recovery, you may choose to use multiple regions and link them together with an event mesh.
-
Latency—For best performance, you should consider the latency from your microservices or client applications to different clouds and regions, which can be affected by the location and cloud you choose. The most ideal scenarios is where the event broker services are co-located with your applications and networked together with an event mesh.
-
Politics and Laws—If you are concerned about data residency due to data sovereignty laws, select the correct regions for your event broker services that match your data residency needs. You may have specific data-residency requirements for your customer data, which may dictate which region you should choose.
You can create event broker services in public datacenters in any of the physical regions listed in the following tables, regardless of your Solace Cloud ownership model type, unless otherwise noted.
- Amazon Web Services Regions
- Google Cloud Platform Regions
- Microsoft Azure Regions
- Other Service Providers
If you don't see a region or cloud provider that you require, contact Solace.
Amazon Web Services Regions
The table below lists some examples of the Amazon Web Service (AWS) regions where Solace currently supports deployments. If you require a region that isn't shown below, contact Solace.
| North America | South America | Europe | Asia Pacific and Africa | Middle East |
|---|---|---|---|---|
|
US East (Northern Virginia) US East (Ohio) US West (Northern California) ** US West (Oregon) Canada Central (Montreal) |
South America (São Paulo) |
Europe (Frankfurt) Europe (Ireland) Europe (London) Europe (Paris) Europe (Milan) Europe (Stockholm) |
Asia Pacific (Tokyo) Asia Pacific (Mumbai) Asia Pacific (Singapore) Asia Pacific (Seoul) Asia Pacific (Jakarta) Australia (Sydney) Australia (Melbourne) Africa (Cape Town) |
Middle East (Tel Aviv) |
** Deployments to this region are limited to two availability zones. See High Availability in Solace Cloud for how availability zones impact your deployment.
Google Cloud Platform Regions
The table below lists some examples of some of the Google Cloud Platform (GCP) regions where Solace currently supports deployments. If you require a region that isn't shown below, contact Solace.
| North America | South America | Europe | Asia Pacific | Australia |
|---|---|---|---|---|
|
South Carolina (us-east1) N. Virginia (us-east4 ) Oregon (us-west1) Los Angeles (us-west2) Iowa (us-central1) Montréal (northamerica-northeast1) |
São Paulo(southamerica-east1) |
Belgium (europe-west1) London (europe-west2) Frankfurt (europe-west3) Netherlands (europe-west4) Finland (europe-north1) Zurich (europe-west6) |
Taiwan (asia-east1) Tokyo (asia-northeast1) Mumbai (asia-south1) Singapore (asia-southeast1) Jakarta (asia-southeast2) |
Sydney (australia-southeast1) |
Microsoft Azure Regions
The table below lists some example of some of the Microsoft Azure regions where Solace currently supports deployments. If you require a region that isn't shown below, contact Solace.
| North America | South America | Europe | Asia Pacific | Australia | Middle East and Africa |
|---|---|---|---|---|---|
|
Central US (Iowa) East US (Virginia) East US 2 (Virginia) North Central US (Illinois) South Central US (Texas) West US (California) West Central US (Wyoming) West US 2 (Washington) Canada Central (Toronto) Canada East (Quebec City) |
Brazil South (São Paulo State) Mexico Central (Queretaro State) |
West Europe (Netherlands) North Europe (Ireland) France South (Marseille) France Central (Paris) UK West (Cardiff) UK South (London) Germany West Central – (Frankfurt) Germany North – (Berlin) Switzerland West (Geneva) Switzerland North (Zurich ) Norway West (Stavanger) Norway East (Oslo) Spain Central (Madrid) Poland Central (Warsaw) Italy North (Milan) |
Southeast Asia (Singapore) East Asia (Hong Kong) China North (Beijing) China North 2 (Beijing) China East (Shanghai) China East 2 (Shanghai) South India (Chennai) Central India (Pune) West India (Mumbai) Japan West (Osaka) Japan East (Tokyo, Saitama) Korea South (Busan) Korea Central (Seoul) New Zealand North (Auckland) |
Australia East (New South Wales) Australia Southeast (Victoria) Australia Central (Canberra) Australia Central 2 (Canberra) |
South Africa West (Cape Town) South Africa North (Johannesburg) UAE North (Dubai) UAE Central (Abu Dhabi) Israel Central (Israel) Qatar Central (Doha) |
Other Service Providers
Huawei Cloud Container Engine (CCE) and Alibaba Cloud Container Service for Kubernetes (ACK) deployments are available upon request. For more information, see Deployments in China.
Identifiers for Datacenter Regions
You can see or request the identifiers for the physical regions of the datacenters of public cloud providers where you can deploy event broker services using:
If you don't see a datacenter in a physical region that you require using either method, contact Solace.
Getting Identifiers for Public Cloud Datacenters Using the Cloud Console
You can use the Create Service page in the Cloud Console to see a list of identifiers and physical region locations of datacenters for the cloud provider you selected. To see a list of identifiers, perform these steps:
- Log in to the Solace Cloud Console if you have not done so yet. The URL to access the Cloud Console differs based on your
- Select Cluster Manager
on the navigation bar. - On the Services page, click Create Service at the top right corner of the page, or, click the Create Service
card. - In the Cloud list, select a cloud provider:
- Select the Region field to see a list of datacenter identifiers and locations for the cloud provider you selected in the Cloud field.
For more information, see Creating Event Broker Services.
Getting Identifiers for Public Cloud Datacenters Using the REST API
To retrieve a list of identifiers and physical region locations of public datacenters for the cloud provider you selected, you can issue a GET request to https://api.solace.cloud/api/v2/datacenters.