Cloud Providers and Regions for Confluent Cloud
Confluent Cloud Kafka clusters and features are available on Amazon Web Services, Microsoft Azure, and Google Cloud.
To request region additions, contact Confluent.
Amazon Web Services (AWS) regions
Following is a list of regions supported for AWS grouped by geographic region.
AWS Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
us-east-1 |
| ✓ | ✓ | ✓ | ✓ | ✓ |
us-east-2 | Ohio, USA | ✓ | ✓ | ✓ | ✓ | ✓ |
us-west-2 | Oregon, USA | ✓ | ✓ | ✓ | ✓ | ✓ |
ca-central-1 | Canada Central | ✓ | ✓ | ✓ | ✓ | |
ca-west-1 | Calgary, Canada | ✓ | ✓ | ✓ | ||
sa-east-1 | São Paulo, Brazil | ✓ | ✓ | ✓ | ✓ |
AWS Region | Location | Flink | Networking |
|---|---|---|---|
us-east-1 |
| ✓ | Public and private |
us-east-2 | Ohio, USA | ✓ | Public and private |
us-west-2 | Oregon, USA | ✓ | Public and private |
ca-central-1 | Canada Central | ✓ | Public and private |
ca-west-1 | Calgary, Canada | ||
sa-east-1 | São Paulo, Brazil | ✓ | Public and private |
AWS Region | Location | Tableflow |
|---|---|---|
us-east-1 |
| ✓ |
us-east-2 | Ohio, USA | ✓ |
us-west-2 | Oregon, USA | ✓ |
ca-central-1 | Canada Central | ✓ |
ca-west-1 | Calgary, Canada | |
sa-east-1 | São Paulo, Brazil | ✓ |
AWS Region | Location | PrivateLink | VPC Peering | Transit Gateway | Private Network Interface (PNI) |
|---|---|---|---|---|---|
us-east-1 |
| ✓ | ✓ | ✓ | ✓ |
us-east-2 | Ohio, USA | ✓ | ✓ | ✓ | ✓ |
us-west-2 | Oregon, USA | ✓ | ✓ | ✓ | ✓ |
ca-central-1 | Canada Central | ✓ | ✓ | ✓ | ✓ |
ca-west-1 | Calgary, Canada | ✓ | ✓ | ✓ | |
sa-east-1 | São Paulo, Brazil | ✓ | ✓ | ✓ | ✓ |
AWS Region | Location | Custom Connectors |
|---|---|---|
us-east-1 |
| ✓ |
us-east-2 | Ohio, USA | ✓ |
us-west-2 | Oregon, USA | ✓ |
ca-central-1 | Canada Central | ✓ |
ca-west-1 | Calgary, Canada | |
sa-east-1 | São Paulo, Brazil | ✓ |
AWS Region | Location | Custom SMT |
|---|---|---|
us-east-1 |
| ✓ |
us-east-2 | Ohio, USA | ✓ |
us-west-2 | Oregon, USA | ✓ |
ca-central-1 | Canada Central | ✓ |
ca-west-1 | Calgary, Canada | |
sa-east-1 | São Paulo, Brazil |
AWS Region | Location | Schema Registry |
|---|---|---|
us-east-1 |
| ✓ |
us-east-2 | Ohio, USA | ✓ |
us-west-2 | Oregon, USA | ✓ |
ca-central-1 | Canada Central | ✓ |
ca-west-1 | Calgary, Canada | ✓ |
sa-east-1 | São Paulo, Brazil | ✓ |
AWS Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
us-east-1 |
| ✓ | ✓ | |
us-east-2 | Ohio, USA | ✓ | ✓ | |
us-west-2 | Oregon, USA | ✓ | ✓ | |
ca-central-1 | Canada Central | ✓ | ✓ | |
ca-west-1 | Calgary, Canada | ✓ | ✓ | |
sa-east-1 | São Paulo, Brazil | ✓ | ✓ |
mTLS for AWS Enterprise clusters is a Limited Availability feature in Confluent Cloud.
mTLS for Enterprise clusters is available on AWS in a Limited Availability manner. This is a fully supported offering available in all AWS regions.
To sign up to try mTLS on Enterprise clusters, use this form: Sign up form for Limited Availability with mTLS Enterprise clusters
AWS Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
ap-east-1 | Hong Kong | ✓ | ✓ | ✓ | ✓ | |
ap-northeast-1 | Tokyo, Japan | ✓ | ✓ | ✓ | ✓ | |
ap-northeast-2 | Seoul, South Korea | ✓ | ✓ | ✓ | ✓ | |
ap-northeast-3 | Osaka, Japan | ✓ | ✓ | ✓ | ✓ | |
ap-south-1 | Mumbai, India | ✓ | ✓ | ✓ | ✓ | ✓ |
ap-south-2 | Hyderabad, India | ✓ | ✓ | ✓ | ✓ | |
ap-southeast-1 | Singapore | ✓ | ✓ | ✓ | ✓ | ✓ |
ap-southeast-2 | Sydney, Australia | ✓ | ✓ | ✓ | ✓ | |
ap-southeast-3 | Jakarta, Indonesia | ✓ | ✓ | ✓ | ✓ | |
ap-southeast-4 | Melbourne, Australia | ✓ | ✓ | ✓ | ✓ | |
ap-southeast-5 | Malaysia | ✓ | ✓ | ✓ | ✓ | |
ap-southeast-7 | Thailand | ✓ | ✓ | ✓ |
AWS Region | Location | Flink | Networking |
|---|---|---|---|
ap-east-1 | Hong Kong | ✓ | Public and private |
ap-northeast-1 | Tokyo, Japan | ✓ | Public and private |
ap-northeast-2 | Seoul, South Korea | ✓ | Public and private |
ap-northeast-3 | Osaka, Japan | ||
ap-south-1 | Mumbai, India | ✓ | Public and private |
ap-south-2 | Hyderabad, India | ||
ap-southeast-1 | Singapore | ✓ | Public and private |
ap-southeast-2 | Sydney, Australia | ✓ | Public and private |
ap-southeast-3 | Jakarta, Indonesia | ✓ | Public and private |
ap-southeast-4 | Melbourne, Australia | ||
ap-southeast-5 | Malaysia | ||
ap-southeast-7 | Thailand |
AWS Region | Location | Tableflow |
|---|---|---|
ap-east-1 | Hong Kong | ✓ |
ap-northeast-1 | Tokyo, Japan | ✓ |
ap-northeast-2 | Seoul, South Korea | ✓ |
ap-northeast-3 | Osaka, Japan | |
ap-south-1 | Mumbai, India | ✓ |
ap-south-2 | Hyderabad, India | |
ap-southeast-1 | Singapore | ✓ |
ap-southeast-2 | Sydney, Australia | ✓ |
ap-southeast-3 | Jakarta, Indonesia | ✓ |
ap-southeast-4 | Melbourne, Australia | |
ap-southeast-5 | Malaysia | |
ap-southeast-7 | Thailand |
AWS Region | Location | PrivateLink | VPC Peering | Transit Gateway | Private Network Interface (PNI) |
|---|---|---|---|---|---|
ap-east-1 | Hong Kong | ✓ | ✓ | ✓ | ✓ |
ap-northeast-1 | Tokyo, Japan | ✓ | ✓ | ✓ | ✓ |
ap-northeast-2 | Seoul, South Korea | ✓ | ✓ | ✓ | ✓ |
ap-northeast-3 | Osaka, Japan | ✓ | ✓ | ✓ | ✓ |
ap-south-1 | Mumbai, India | ✓ | ✓ | ✓ | ✓ |
ap-south-2 | Hyderabad, India | ✓ | ✓ | ✓ | ✓ |
ap-southeast-1 | Singapore | ✓ | ✓ | ✓ | ✓ |
ap-southeast-2 | Sydney, Australia | ✓ | ✓ | ✓ | ✓ |
ap-southeast-3 | Jakarta, Indonesia | ✓ | ✓ | ✓ | ✓ |
ap-southeast-4 | Melbourne, Australia | ✓ | ✓ | ✓ | ✓ |
ap-southeast-5 | Malaysia | ✓ | ✓ | ✓ | ✓ |
ap-southeast-7 | Thailand | ✓ | ✓ | ✓ |
AWS Region | Location | Custom Connectors |
|---|---|---|
ap-east-1 | Hong Kong | ✓ |
ap-northeast-1 | Tokyo, Japan | ✓ |
ap-northeast-2 | Seoul, South Korea | ✓ |
ap-northeast-3 | Osaka, Japan | ✓ |
ap-south-1 | Mumbai, India | ✓ |
ap-south-2 | Hyderabad, India | ✓ |
ap-southeast-1 | Singapore | ✓ |
ap-southeast-2 | Sydney, Australia | ✓ |
ap-southeast-3 | Jakarta, Indonesia | ✓ |
ap-southeast-4 | Melbourne, Australia | ✓ |
ap-southeast-5 | Malaysia | |
ap-southeast-7 | Thailand |
AWS Region | Location | Custom SMT |
|---|---|---|
ap-east-1 | Hong Kong | |
ap-northeast-1 | Tokyo, Japan | |
ap-northeast-2 | Seoul, South Korea | |
ap-northeast-3 | Osaka, Japan | |
ap-south-1 | Mumbai, India | ✓ |
ap-south-2 | Hyderabad, India | |
ap-southeast-1 | Singapore | ✓ |
ap-southeast-2 | Sydney, Australia | ✓ |
ap-southeast-3 | Jakarta, Indonesia | |
ap-southeast-4 | Melbourne, Australia | |
ap-southeast-5 | Malaysia | |
ap-southeast-7 | Thailand |
AWS Region | Location | Schema Registry |
|---|---|---|
ap-east-1 | Hong Kong | ✓ |
ap-northeast-1 | Tokyo, Japan | ✓ |
ap-northeast-2 | Seoul, South Korea | ✓ |
ap-northeast-3 | Osaka, Japan | ✓ |
ap-south-1 | Mumbai, India | ✓ |
ap-south-2 | Hyderabad, India | ✓ |
ap-southeast-1 | Singapore | ✓ |
ap-southeast-2 | Sydney, Australia | ✓ |
ap-southeast-3 | Jakarta, Indonesia | ✓ |
ap-southeast-4 | Melbourne, Australia | ✓ |
ap-southeast-5 | Malaysia | ✓ |
ap-southeast-7 | Thailand | ✓ |
AWS Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
ap-east-1 | Hong Kong | ✓ | ✓ | |
ap-northeast-1 | Tokyo, Japan | ✓ | ✓ | |
ap-northeast-2 | Seoul, South Korea | ✓ | ✓ | |
ap-northeast-3 | Osaka, Japan | ✓ | ✓ | |
ap-south-1 | Mumbai, India | ✓ | ✓ | |
ap-south-2 | Hyderabad, India | ✓ | ✓ | |
ap-southeast-1 | Singapore | ✓ | ✓ | |
ap-southeast-2 | Sydney, Australia | ✓ | ✓ | |
ap-southeast-3 | Jakarta, Indonesia | ✓ | ✓ | |
ap-southeast-4 | Melbourne, Australia | ✓ | ✓ | |
ap-southeast-5 | Malaysia | ✓ | ✓ | |
ap-southeast-7 | Thailand | ✓ | ✓ |
mTLS for AWS Enterprise clusters is a Limited Availability feature in Confluent Cloud.
mTLS for Enterprise clusters is available on AWS in a Limited Availability manner. This is a fully supported offering available in all AWS regions.
To sign up to try mTLS on Enterprise clusters, use this form: Sign up form for Limited Availability with mTLS Enterprise clusters
AWS Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ | ✓ | ✓ | ✓ | ✓ |
eu-central-2 | Zurich, Switzerland | ✓ | ✓ | ✓ | ✓ | |
eu-north-1 | Stockholm, Sweden | ✓ | ✓ | ✓ | ✓ | |
eu-south-1 | Milan, Italy | ✓ | ✓ | ✓ | ✓ | |
eu-south-2 | Spain | ✓ | ✓ | ✓ | ✓ | |
eu-west-1 | Ireland | ✓ | ✓ | ✓ | ✓ | |
eu-west-2 | London, UK | ✓ | ✓ | ✓ | ✓ | |
eu-west-3 | Paris, France | ✓ | ✓ | ✓ | ✓ |
AWS Region | Location | Flink | Networking |
|---|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ | Public and private |
eu-central-2 | Zurich, Switzerland | ||
eu-north-1 | Stockholm, Sweden | ✓ | Public and private |
eu-south-1 | Milan, Italy | ✓ | Public and private |
eu-south-2 | Spain | ||
eu-west-1 | Ireland | ✓ | Public and private |
eu-west-2 | London, UK | ✓ | Public and private |
eu-west-3 | Paris, France | ✓ | Public and private |
AWS Region | Location | Tableflow |
|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ |
eu-central-2 | Zurich, Switzerland | |
eu-north-1 | Stockholm, Sweden | ✓ |
eu-south-1 | Milan, Italy | ✓ |
eu-south-2 | Spain | |
eu-west-1 | Ireland | ✓ |
eu-west-2 | London, UK | ✓ |
eu-west-3 | Paris, France | ✓ |
AWS Region | Location | PrivateLink | VPC Peering | Transit Gateway | Private Network Interface (PNI) |
|---|---|---|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ | ✓ | ✓ | ✓ |
eu-central-2 | Zurich, Switzerland | ✓ | ✓ | ✓ | ✓ |
eu-north-1 | Stockholm, Sweden | ✓ | ✓ | ✓ | ✓ |
eu-south-1 | Milan, Italy | ✓ | ✓ | ✓ | ✓ |
eu-south-2 | Spain | ✓ | ✓ | ✓ | ✓ |
eu-west-1 | Ireland | ✓ | ✓ | ✓ | ✓ |
eu-west-2 | London, UK | ✓ | ✓ | ✓ | ✓ |
eu-west-3 | Paris, France | ✓ | ✓ | ✓ | ✓ |
AWS Region | Location | Custom Connectors |
|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ |
eu-central-2 | Zurich, Switzerland | ✓ |
eu-north-1 | Stockholm, Sweden | ✓ |
eu-south-1 | Milan, Italy | ✓ |
eu-south-2 | Spain | ✓ |
eu-west-1 | Ireland | ✓ |
eu-west-2 | London, UK | ✓ |
eu-west-3 | Paris, France | ✓ |
AWS Region | Location | Custom SMT |
|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ |
eu-central-2 | Zurich, Switzerland | |
eu-north-1 | Stockholm, Sweden | |
eu-south-1 | Milan, Italy | |
eu-south-2 | Spain | |
eu-west-1 | Ireland | ✓ |
eu-west-2 | London, UK | ✓ |
eu-west-3 | Paris, France |
AWS Region | Location | Schema Registry |
|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ |
eu-central-2 | Zurich, Switzerland | ✓ |
eu-north-1 | Stockholm, Sweden | ✓ |
eu-south-1 | Milan, Italy | ✓ |
eu-south-2 | Spain | ✓ |
eu-west-1 | Ireland | ✓ |
eu-west-2 | London, UK | ✓ |
eu-west-3 | Paris, France | ✓ |
AWS Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
eu-central-1 | Frankfurt, Germany | ✓ | ✓ | |
eu-central-2 | Zurich, Switzerland | ✓ | ✓ | |
eu-north-1 | Stockholm, Sweden | ✓ | ✓ | |
eu-south-1 | Milan, Italy | ✓ | ✓ | |
eu-south-2 | Spain | ✓ | ✓ | |
eu-west-1 | Ireland | ✓ | ✓ | |
eu-west-2 | London, UK | ✓ | ✓ | |
eu-west-3 | Paris, France | ✓ | ✓ |
mTLS for AWS Enterprise clusters is a Limited Availability feature in Confluent Cloud.
mTLS for Enterprise clusters is available on AWS in a Limited Availability manner. This is a fully supported offering available in all AWS regions.
To sign up to try mTLS on Enterprise clusters, use this form: Sign up form for Limited Availability with mTLS Enterprise clusters
AWS Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
me-south-1 | Bahrain | ✓ | ✓ | ✓ | ✓ | |
me-central-1 | UAE | ✓ | ✓ | ✓ | ✓ | |
af-south-1 | Cape Town, South Africa | ✓ | ✓ | ✓ | ✓ | |
il-central-1 | Tel Aviv, Israel | ✓ | ✓ | ✓ |
AWS Region | Location | Flink | Networking |
|---|---|---|---|
me-south-1 | Bahrain | ✓ | Public and private |
me-central-1 | UAE | ✓ | Public and private |
af-south-1 | Cape Town, South Africa | ✓ | Public and private |
il-central-1 | Tel Aviv, Israel |
AWS Region | Location | Tableflow |
|---|---|---|
me-south-1 | Bahrain | ✓ |
me-central-1 | UAE | ✓ |
af-south-1 | Cape Town, South Africa | ✓ |
il-central-1 | Tel Aviv, Israel |
AWS Region | Location | PrivateLink | VPC Peering | Transit Gateway | Private Network Interface (PNI) |
|---|---|---|---|---|---|
me-south-1 | Bahrain | ✓ | ✓ | ✓ | ✓ |
me-central-1 | UAE | ✓ | ✓ | ✓ | ✓ |
af-south-1 | Cape Town, South Africa | ✓ | ✓ | ✓ | ✓ |
il-central-1 | Tel Aviv, Israel | ✓ | ✓ | ✓ |
AWS Region | Location | Custom Connectors |
|---|---|---|
me-south-1 | Bahrain | ✓ |
me-central-1 | UAE | ✓ |
af-south-1 | Cape Town, South Africa | ✓ |
il-central-1 | Tel Aviv, Israel |
AWS Region | Location | Custom SMT |
|---|---|---|
me-south-1 | Bahrain | |
me-central-1 | UAE | |
af-south-1 | Cape Town, South Africa | |
il-central-1 | Tel Aviv, Israel |
AWS Region | Location | Schema Registry |
|---|---|---|
me-south-1 | Bahrain | ✓ |
me-central-1 | UAE | ✓ |
af-south-1 | Cape Town, South Africa | ✓ |
il-central-1 | Tel Aviv, Israel | ✓ |
AWS Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
me-south-1 | Bahrain | ✓ | ✓ | |
me-central-1 | UAE | ✓ | ✓ | |
af-south-1 | Cape Town, South Africa | ✓ | ✓ | |
il-central-1 | Tel Aviv, Israel | ✓ | ✓ |
mTLS for AWS Enterprise clusters is a Limited Availability feature in Confluent Cloud.
mTLS for Enterprise clusters is available on AWS in a Limited Availability manner. This is a fully supported offering available in all AWS regions.
To sign up to try mTLS on Enterprise clusters, use this form: Sign up form for Limited Availability with mTLS Enterprise clusters
Feature | |||||
|---|---|---|---|---|---|
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | |||
✓ | |||||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | ✓ | ||
✓ | |||||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ||||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ (*) | |||
✓ | |||||
✓ |
* Stream sharing doesn’t support all private networking options.
Feature | PrivateLink (Inbound) | PrivateLink (Outbound) | |||
|---|---|---|---|---|---|
Enterprise cluster | ✓ | ||||
Freight cluster | ✓ | ||||
Dedicated cluster | ✓ | ✓ | |||
Connect | ✓ | ✓ | |||
Flink | ✓ | ✓ | ✓ Serverless | Dedicated | ||
Schema Registry | ✓ | ✓ | ✓ Serverless | Dedicated | ||
Flink external table lookups | |||||
Inferences for external AI models | |||||
Connect with Enterprise Kafka clusters | |||||
Connect with Dedicated Kafka clusters | |||||
Cluster Linking with Enterprise Kafka clusters |
AWS GovCloud
In addition to the commercial AWS regions, Confluent supports AWS GovCloud regions with Confluent Cloud for Government. AWS GovCloud regions meet stringent U.S. government security requirements. For more information, see AWS GovCloud documentation and Confluent Cloud for Government documentation.
AWS Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
us-gov-west-1 | AWS GovCloud US-West | ✓ | ||||
us-gov-east-1 | AWS GovCloud US-East | ✓ |
AWS Region | Location | PrivateLink | VPC Peering | Transit Gateway | Private Network Interface (PNI) |
|---|---|---|---|---|---|
us-gov-west-1 | AWS GovCloud US-West | ✓ | ✓ | ✓ | |
us-gov-east-1 | AWS GovCloud US-East | ✓ | ✓ | ✓ |
Microsoft Azure (Azure) regions
Following is a list of regions supported for Azure grouped by geographic region.
Azure Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
canadacentral | Toronto, Canada | ✓ | ✓ | ✓ | ✓ | |
mexicocentral | Mexico Central | ✓ | ✓ | ✓ | ||
brazilsouth | Sao Paulo state, Brazil | ✓ | ✓ | ✓ | ✓ | |
centralus | Iowa, USA | ✓ | ✓ | ✓ | ✓ | |
eastus | Virginia, USA | ✓ | ✓ | ✓ | ✓ | |
eastus2 | Virginia, USA | ✓ | ✓ | ✓ | ✓ | |
southcentralus | Texas, USA | ✓ | ✓ | ✓ | ✓ | |
westus2 | Washington, USA | ✓ | ✓ | ✓ | ✓ | |
westus3 | Phoenix, USA | ✓ | ✓ | ✓ | ✓ |
Azure Region | Location | Flink | Networking |
|---|---|---|---|
canadacentral | Toronto, Canada | ✓ | Public and private |
mexicocentral | Mexico Central | ||
brazilsouth | Sao Paulo state, Brazil | ✓ | Public and private |
centralus | Iowa, USA | ✓ | Public and private |
eastus | Virginia, USA | ✓ | Public and private |
eastus2 | Virginia, USA | ✓ | Public and private |
southcentralus | Texas, USA | ✓ | Public and private |
westus2 | Washington, USA | ✓ | Public and private |
westus3 | Phoenix, USA | ✓ | Public and private |
Azure Region | Location | Tableflow |
|---|---|---|
canadacentral | Toronto, Canada | |
mexicocentral | Mexico Central | |
brazilsouth | Sao Paulo state, Brazil | |
centralus | Iowa, USA | |
eastus | Virginia, USA | |
eastus2 | Virginia, USA | ✓ (Early Access) |
southcentralus | Texas, USA | |
westus2 | Washington, USA | |
westus3 | Phoenix, USA |
Note
Tableflow is available for Early Access in these Azure regions.
An Early Access feature is a component of Confluent Cloud introduced to gain feedback. This feature should be used only for evaluation and non-production testing purposes or to provide feedback to Confluent, particularly as it becomes more widely available in follow-on preview editions.
Early Access Program features are intended for evaluation use in development and testing environments only, and not for production use. Early Access Program features are provided: (a) without support; (b) “AS IS”; and (c) without indemnification, warranty, or condition of any kind. No service level commitment will apply to Early Access Program features. Early Access Program features are considered to be a Proof of Concept as defined in the Confluent Cloud Terms of Service. Confluent may discontinue providing preview releases of the Early Access Program features at any time in Confluent’s sole discretion.
If you would like to participate in the early access program, contact Confluent.
Azure Region | Location | Private Link | VNet Peering |
|---|---|---|---|
canadacentral | Toronto, Canada | ✓ | ✓ |
mexicocentral | Mexico Central | ✓ | ✓ |
brazilsouth | Sao Paulo state, Brazil | ✓ | ✓ |
centralus | Iowa, USA | ✓ | ✓ |
eastus | Virginia, USA | ✓ | ✓ |
eastus2 | Virginia, USA | ✓ | ✓ |
southcentralus | Texas, USA | ✓ | ✓ |
westus2 | Washington, USA | ✓ | ✓ |
westus3 | Phoenix, USA | ✓ | ✓ |
Azure Region | Location | Custom Connectors |
|---|---|---|
canadacentral | Toronto, Canada | ✓ |
mexicocentral | Mexico Central | |
brazilsouth | Sao Paulo state, Brazil | ✓ |
centralus | Iowa, USA | ✓ |
eastus | Virginia, USA | ✓ |
eastus2 | Virginia, USA | ✓ |
southcentralus | Texas, USA | ✓ |
westus2 | Washington, USA | ✓ |
westus3 | Phoenix, USA | ✓ |
Azure Region | Location | Custom SMT |
|---|---|---|
canadacentral | Toronto, Canada | |
mexicocentral | Mexico Central | |
brazilsouth | Sao Paulo state, Brazil | ✓ |
centralus | Iowa, USA | ✓ |
eastus | Virginia, USA | ✓ |
eastus2 | Virginia, USA | ✓ |
southcentralus | Texas, USA | |
westus2 | Washington, USA | ✓ |
westus3 | Phoenix, USA |
Azure Region | Location | Schema Registry |
|---|---|---|
canadacentral | Toronto, Canada | ✓ |
mexicocentral | Mexico Central | ✓ |
brazilsouth | Sao Paulo state, Brazil | ✓ |
centralus | Iowa, USA | ✓ |
eastus | Virginia, USA | ✓ |
eastus2 | Virginia, USA | ✓ |
southcentralus | Texas, USA | ✓ |
westus2 | Washington, USA | ✓ |
westus3 | Phoenix, USA | ✓ |
Azure Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
canadacentral | Toronto, Canada | ✓ | ||
mexicocentral | Mexico Central | ✓ | ||
brazilsouth | Sao Paulo state, Brazil | ✓ | ||
centralus | Iowa, USA | ✓ | ||
eastus | Virginia, USA | ✓ | ||
eastus2 | Virginia, USA | ✓ | ||
southcentralus | Texas, USA | ✓ | ||
westus2 | Washington, USA | ✓ | ||
westus3 | Phoenix, USA | ✓ |
Azure Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
australiaeast | New South Wales, Australia | ✓ | ✓ | ✓ | ✓ | |
centralindia | Pune, India | ✓ | ✓ | ✓ | ✓ | |
eastasia | Hong Kong | ✓ | ✓ | ✓ | ✓ | |
japaneast | Tokyo, Japan | ✓ | ✓ | ✓ | ✓ | |
koreacentral | Seoul, South Korea | ✓ | ✓ | ✓ | ✓ | |
southeastasia | Singapore | ✓ | ✓ | ✓ | ✓ | |
newzealandnorth | New Zealand North | ✓ | ✓ | ✓ | ✓ |
Azure Region | Location | Flink | Networking |
|---|---|---|---|
australiaeast | New South Wales, Australia | ✓ | Public and private |
centralindia | Pune, India | ✓ | Public and private |
eastasia | Hong Kong | ✓ | Public and private |
japaneast | Tokyo, Japan | ✓ | Public and private |
koreacentral | Seoul, South Korea | ||
southeastasia | Singapore | ✓ | Public and private |
newzealandnorth | New Zealand North | ✓ | Public and private |
Azure Region | Location | Tableflow |
|---|---|---|
australiaeast | New South Wales, Australia | |
centralindia | Pune, India | |
eastasia | Hong Kong | |
japaneast | Tokyo, Japan | |
koreacentral | Seoul, South Korea | |
southeastasia | Singapore | |
newzealandnorth | New Zealand North |
Azure Region | Location | Private Link | VNet Peering |
|---|---|---|---|
australiaeast | New South Wales, Australia | ✓ | ✓ |
centralindia | Pune, India | ✓ | ✓ |
eastasia | Hong Kong | ✓ | ✓ |
japaneast | Tokyo, Japan | ✓ | ✓ |
koreacentral | Seoul, South Korea | ✓ | ✓ |
southeastasia | Singapore | ✓ | ✓ |
newzealandnorth | New Zealand North | ✓ | ✓ |
Azure Region | Location | Custom Connectors |
|---|---|---|
australiaeast | New South Wales, Australia | ✓ |
centralindia | Pune, India | ✓ |
eastasia | Hong Kong | |
japaneast | Tokyo, Japan | ✓ |
koreacentral | Seoul, South Korea | ✓ |
southeastasia | Singapore | ✓ |
newzealandnorth | New Zealand North | ✓ |
Azure Region | Location | Custom SMT |
|---|---|---|
australiaeast | New South Wales, Australia | |
centralindia | Pune, India | ✓ |
eastasia | Hong Kong | |
japaneast | Tokyo, Japan | |
koreacentral | Seoul, South Korea | |
southeastasia | Singapore | ✓ |
newzealandnorth | New Zealand North |
Azure Region | Location | Schema Registry |
|---|---|---|
australiaeast | New South Wales, Australia | ✓ |
centralindia | Pune, India | ✓ |
eastasia | Hong Kong | ✓ |
japaneast | Tokyo, Japan | ✓ |
koreacentral | Seoul, South Korea | ✓ |
southeastasia | Singapore | ✓ |
newzealandnorth | New Zealand North | ✓ |
Azure Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
australiaeast | New South Wales, Australia | ✓ | ||
centralindia | Pune, India | ✓ | ||
eastasia | Hong Kong | ✓ | ||
japaneast | Tokyo, Japan | ✓ | ||
koreacentral | Seoul, South Korea | ✓ | ||
southeastasia | Singapore | ✓ | ||
newzealandnorth | New Zealand North | ✓ |
Azure Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
francecentral | Paris, France | ✓ | ✓ | ✓ | ✓ | |
germanywestcentral | Frankfurt, Germany | ✓ | ✓ | ✓ | ✓ | |
northeurope | Ireland | ✓ | ✓ | ✓ | ✓ | |
norwayeast | Oslo, Norway | ✓ | ✓ | ✓ | ✓ | |
swedencentral | Gävle, Sweden | ✓ | ✓ | ✓ | ✓ | |
switzerlandnorth | Zurich, Switzerland | ✓ | ✓ | ✓ | ✓ | |
uksouth | London, UK | ✓ | ✓ | ✓ | ✓ | |
westeurope | Netherlands | ✓ | ✓ | ✓ | ✓ | |
italynorth | Milan, Italy | ✓ | ✓ | ✓ | ||
spaincentral | Spain | ✓ | ✓ | ✓ | ✓ |
Azure Region | Location | Flink | Networking |
|---|---|---|---|
francecentral | Paris, France | ✓ | Public and private |
germanywestcentral | Frankfurt, Germany | ✓ | Public and private |
northeurope | Ireland | ✓ | Public and private |
norwayeast | Oslo, Norway | ✓ | Public and private |
swedencentral | Gävle, Sweden | ||
switzerlandnorth | Zurich, Switzerland | ✓ | Public and private |
uksouth | London, UK | ✓ | Public and private |
westeurope | Netherlands | ✓ | Public and private |
italynorth | Milan, Italy | ||
spaincentral | Spain | ✓ | Public and private |
Azure Region | Location | Tableflow |
|---|---|---|
francecentral | Paris, France | |
germanywestcentral | Frankfurt, Germany | |
northeurope | Ireland | |
norwayeast | Oslo, Norway | |
swedencentral | Gävle, Sweden | |
switzerlandnorth | Zurich, Switzerland | |
uksouth | London, UK | |
westeurope | Netherlands | ✓ (Early Access) |
italynorth | Milan, Italy | |
spaincentral | Spain |
Note
Tableflow is available for Early Access in these Azure regions.
An Early Access feature is a component of Confluent Cloud introduced to gain feedback. This feature should be used only for evaluation and non-production testing purposes or to provide feedback to Confluent, particularly as it becomes more widely available in follow-on preview editions.
Early Access Program features are intended for evaluation use in development and testing environments only, and not for production use. Early Access Program features are provided: (a) without support; (b) “AS IS”; and (c) without indemnification, warranty, or condition of any kind. No service level commitment will apply to Early Access Program features. Early Access Program features are considered to be a Proof of Concept as defined in the Confluent Cloud Terms of Service. Confluent may discontinue providing preview releases of the Early Access Program features at any time in Confluent’s sole discretion.
If you would like to participate in the early access program, contact Confluent.
Azure Region | Location | Private Link | VNet Peering |
|---|---|---|---|
francecentral | Paris, France | ✓ | ✓ |
germanywestcentral | Frankfurt, Germany | ✓ | ✓ |
northeurope | Ireland | ✓ | ✓ |
norwayeast | Oslo, Norway | ✓ | ✓ |
swedencentral | Gävle, Sweden | ✓ | ✓ |
switzerlandnorth | Zurich, Switzerland | ✓ | ✓ |
uksouth | London, UK | ✓ | ✓ |
westeurope | Netherlands | ✓ | ✓ |
italynorth | Milan, Italy | ✓ | ✓ |
spaincentral | Spain | ✓ | ✓ |
Azure Region | Location | Custom Connectors |
|---|---|---|
francecentral | Paris, France | ✓ |
germanywestcentral | Frankfurt, Germany | ✓ |
northeurope | Ireland | ✓ |
norwayeast | Oslo, Norway | ✓ |
swedencentral | Gävle, Sweden | ✓ |
switzerlandnorth | Zurich, Switzerland | ✓ |
uksouth | London, UK | ✓ |
westeurope | Netherlands | ✓ |
italynorth | Milan, Italy | |
spaincentral | Spain | ✓ |
Azure Region | Location | Custom SMT |
|---|---|---|
francecentral | Paris, France | |
germanywestcentral | Frankfurt, Germany | |
northeurope | Ireland | ✓ |
norwayeast | Oslo, Norway | |
swedencentral | Gävle, Sweden | |
switzerlandnorth | Zurich, Switzerland | |
uksouth | London, UK | ✓ |
westeurope | Netherlands | ✓ |
italynorth | Milan, Italy | |
spaincentral | Spain |
Azure Region | Location | Schema Registry |
|---|---|---|
francecentral | Paris, France | ✓ |
germanywestcentral | Frankfurt, Germany | ✓ |
northeurope | Ireland | ✓ |
norwayeast | Oslo, Norway | ✓ |
swedencentral | Gävle, Sweden | ✓ |
switzerlandnorth | Zurich, Switzerland | ✓ |
uksouth | London, UK | ✓ |
westeurope | Netherlands | ✓ |
italynorth | Milan, Italy | ✓ |
spaincentral | Spain | ✓ |
Azure Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
francecentral | Paris, France | ✓ | ||
germanywestcentral | Frankfurt, Germany | ✓ | ||
northeurope | Ireland | ✓ | ||
norwayeast | Oslo, Norway | ✓ | ||
swedencentral | Gävle, Sweden | ✓ | ||
switzerlandnorth | Zurich, Switzerland | ✓ | ||
uksouth | London, UK | ✓ | ||
westeurope | Netherlands | ✓ | ||
italynorth | Milan, Italy | ✓ | ||
spaincentral | Spain | ✓ |
Azure Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
southafricanorth | Johannesburg, South Africa | ✓ | ✓ | ✓ | ✓ | |
uaenorth | Dubai, UAE | ✓ | ✓ | ✓ | ✓ | |
qatarcentral | Doha, Qatar | ✓ | ✓ | ✓ |
Azure Region | Location | Flink | Networking |
|---|---|---|---|
southafricanorth | Johannesburg, South Africa | ||
uaenorth | Dubai, UAE | ✓ | Public and private |
qatarcentral | Doha, Qatar |
Azure Region | Location | Tableflow |
|---|---|---|
southafricanorth | Johannesburg, South Africa | |
uaenorth | Dubai, UAE | |
qatarcentral | Doha, Qatar |
Azure Region | Location | Private Link | VNet Peering |
|---|---|---|---|
southafricanorth | Johannesburg, South Africa | ✓ | ✓ |
uaenorth | Dubai, UAE | ✓ | ✓ |
qatarcentral | Doha, Qatar | ✓ | ✓ |
Azure Region | Location | Custom Connectors |
|---|---|---|
southafricanorth | Johannesburg, South Africa | ✓ |
uaenorth | Dubai, UAE | ✓ |
qatarcentral | Doha, Qatar |
Azure Region | Location | Custom SMT |
|---|---|---|
southafricanorth | Johannesburg, South Africa | |
uaenorth | Dubai, UAE | |
qatarcentral | Doha, Qatar |
Azure Region | Location | Schema Registry |
|---|---|---|
southafricanorth | Johannesburg, South Africa | ✓ |
uaenorth | Dubai, UAE | ✓ |
qatarcentral | Doha, Qatar | ✓ |
Azure Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
southafricanorth | Johannesburg, South Africa | ✓ | ||
uaenorth | Dubai, UAE | ✓ | ||
qatarcentral | Doha, Qatar | ✓ |
Feature | |||||
|---|---|---|---|---|---|
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | |||
✓ | |||||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | ✓ | ||
✓ | |||||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ||||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ (*) | |||
✓ | |||||
✓ |
* Stream sharing doesn’t support all private networking options.
Feature | PrivateLink (Inbound) | PrivateLink (Outbound) | |
|---|---|---|---|
Enterprise cluster | |||
Dedicated cluster | ✓ | ||
Connect | ✓ | ||
Flink | ✓ | ✓ Serverless | Dedicated | |
Schema Registry | ✓ | ✓ Serverless | Dedicated | |
Connect with Dedicated Kafka clusters | |||
Connect with Enterprise Kafka clusters |
Jio Cloud
Jio regions provide a maximum SLA of 99.95%. You must be a Jio customer to use Confluent Cloud in Jio regions. For more information, see How do I sign up for Confluent Cloud in Jio regions?.
- Considerations:
Only single-zone Dedicated Kafka clusters are available in Jio regions.
Stream Governance packages purchased in Jio regions support a maximum SLA of 99.95%.
Azure VNet Peering for Dedicated clusters is the only private networking option available
No other features are supported in Jio regions.
Google Cloud regions
Following is a list of regions supported for Google Cloud grouped by geographic region.
GCP Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
northamerica-northeast1 | Montreal, Canada | ✓ | ✓ | ✓ | ✓ | |
northamerica-northeast2 | Toronto, Canada | ✓ | ✓ | ✓ | ✓ | |
southamerica-east1 | São Paulo, Brazil | ✓ | ✓ | ✓ | ✓ | |
southamerica-west1 | Santiago, Chile | ✓ | ✓ | ✓ | ||
us-central1 | Iowa, USA | ✓ | ✓ | ✓ | ✓ | |
us-east1 |
| ✓ | ✓ | ✓ | ✓ | |
us-east4 |
| ✓ | ✓ | ✓ | ✓ | |
us-west1 | Oregon, USA | ✓ | ✓ | ✓ | ✓ | |
us-west2 | Los Angeles, USA | ✓ | ✓ | ✓ | ✓ | |
us-west3 | Salt Lake City, USA | ✓ | ✓ | ✓ | ✓ | |
us-west4 | Las Vegas, USA | ✓ | ✓ | ✓ | ✓ | |
us-south1 | Dallas, USA | ✓ | ✓ | ✓ |
GCP Region | Location | Flink | Networking |
|---|---|---|---|
northamerica-northeast1 | Montreal, Canada | ✓ | Public and private |
northamerica-northeast2 | Toronto, Canada | ✓ | Public and private |
southamerica-east1 | São Paulo, Brazil | ✓ | Public and private |
southamerica-west1 | Santiago, Chile | ||
us-central1 | Iowa, USA | ✓ | Public and private |
us-east1 |
| ✓ | Public and private |
us-east4 |
| ✓ | Public and private |
us-west1 | Oregon, USA | ✓ | Public and private |
us-west2 | Los Angeles, USA | ✓ | Public and private |
us-west3 | Salt Lake City, USA | ||
us-west4 | Las Vegas, USA | ✓ | Public and private |
us-south1 | Dallas, USA |
GCP Region | Location | Tableflow |
|---|---|---|
northamerica-northeast1 | Montreal, Canada | |
northamerica-northeast2 | Toronto, Canada | |
southamerica-east1 | São Paulo, Brazil | |
southamerica-west1 | Santiago, Chile | |
us-central1 | Iowa, USA | |
us-east1 |
| |
us-east4 |
| |
us-west1 | Oregon, USA | |
us-west2 | Los Angeles, USA | |
us-west3 | Salt Lake City, USA | |
us-west4 | Las Vegas, USA | |
us-south1 | Dallas, USA |
GCP Region | Location | Private Service Connect | VPC Peering |
|---|---|---|---|
northamerica-northeast1 | Montreal, Canada | ✓ | ✓ |
northamerica-northeast2 | Toronto, Canada | ✓ | ✓ |
southamerica-east1 | São Paulo, Brazil | ✓ | ✓ |
southamerica-west1 | Santiago, Chile | ✓ | ✓ |
us-central1 | Iowa, USA | ✓ | ✓ |
us-east1 |
| ✓ | ✓ |
us-east4 |
| ✓ | ✓ |
us-west1 | Oregon, USA | ✓ | ✓ |
us-west2 | Los Angeles, USA | ✓ | ✓ |
us-west3 | Salt Lake City, USA | ✓ | ✓ |
us-west4 | Las Vegas, USA | ✓ | ✓ |
us-south1 | Dallas, USA | ✓ | ✓ |
GCP Region | Location | Custom Connectors |
|---|---|---|
northamerica-northeast1 | Montreal, Canada | |
northamerica-northeast2 | Toronto, Canada | |
southamerica-east1 | São Paulo, Brazil | |
southamerica-west1 | Santiago, Chile | |
us-central1 | Iowa, USA | ✓ |
us-east1 |
| ✓ |
us-east4 |
| ✓ |
us-west1 | Oregon, USA | ✓ |
us-west2 | Los Angeles, USA | ✓ |
us-west3 | Salt Lake City, USA | |
us-west4 | Las Vegas, USA | ✓ |
us-south1 | Dallas, USA |
GCP Region | Location | Custom SMT |
|---|---|---|
northamerica-northeast1 | Montreal, Canada | |
northamerica-northeast2 | Toronto, Canada | |
southamerica-east1 | São Paulo, Brazil | |
southamerica-west1 | Santiago, Chile | |
us-central1 | Iowa, USA | |
us-east1 |
| |
us-east4 |
| |
us-west1 | Oregon, USA | |
us-west2 | Los Angeles, USA | |
us-west3 | Salt Lake City, USA | |
us-west4 | Las Vegas, USA | |
us-south1 | Dallas, USA |
GCP Region | Location | Schema Registry |
|---|---|---|
northamerica-northeast1 | Montreal, Canada | ✓ |
northamerica-northeast2 | Toronto, Canada | ✓ |
southamerica-east1 | São Paulo, Brazil | ✓ |
southamerica-west1 | Santiago, Chile | ✓ |
us-central1 | Iowa, USA | ✓ |
us-east1 |
| ✓ |
us-east4 |
| ✓ |
us-west1 | Oregon, USA | ✓ |
us-west2 | Los Angeles, USA | ✓ |
us-west3 | Salt Lake City, USA | ✓ |
us-west4 | Las Vegas, USA | ✓ |
us-south1 | Dallas, USA | ✓ |
GCP Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
northamerica-northeast1 | Montreal, Canada | ✓ | ||
northamerica-northeast2 | Toronto, Canada | ✓ | ||
southamerica-east1 | São Paulo, Brazil | ✓ | ||
southamerica-west1 | Santiago, Chile | ✓ | ||
us-central1 | Iowa, USA | ✓ | ||
us-east1 |
| ✓ | ||
us-east4 |
| ✓ | ||
us-west1 | Oregon, USA | ✓ | ||
us-west2 | Los Angeles, USA | ✓ | ||
us-west3 | Salt Lake City, USA | ✓ | ||
us-west4 | Las Vegas, USA | ✓ | ||
us-south1 | Dallas, USA | ✓ |
GCP Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
asia-east1 | Taiwan | ✓ | ✓ | ✓ | ||
asia-east2 | Hong Kong | ✓ | ✓ | ✓ | ||
asia-northeast1 | Tokyo, Japan | ✓ | ✓ | ✓ | ✓ | |
asia-northeast2 | Osaka, Japan | ✓ | ✓ | ✓ | ||
asia-northeast3 | Seoul, South Korea | ✓ | ✓ | ✓ | ||
asia-south1 | Mumbai, India | ✓ | ✓ | ✓ | ✓ | |
asia-south2 | Delhi, India | ✓ | ✓ | ✓ | ✓ | |
asia-southeast1 | Singapore | ✓ | ✓ | ✓ | ✓ | |
asia-southeast2 | Jakarta, Indonesia | ✓ | ✓ | ✓ | ✓ | |
australia-southeast1 | Sydney, Australia | ✓ | ✓ | ✓ | ✓ | |
australia-southeast2 | Melbourne, Australia | ✓ | ✓ | ✓ |
GCP Region | Location | Flink | Networking |
|---|---|---|---|
asia-east1 | Taiwan | ||
asia-east2 | Hong Kong | ||
asia-northeast1 | Tokyo, Japan | ✓ | Public and private |
asia-northeast2 | Osaka, Japan | ||
asia-northeast3 | Seoul, South Korea | ||
asia-south1 | Mumbai, India | ✓ | Public and private |
asia-south2 | Delhi, India | ✓ | Public and private |
asia-southeast1 | Singapore | ✓ | Public and private |
asia-southeast2 | Jakarta, Indonesia | ✓ | Public and private |
australia-southeast1 | Sydney, Australia | ✓ | Public and private |
australia-southeast2 | Melbourne, Australia |
GCP Region | Location | Tableflow |
|---|---|---|
asia-east1 | Taiwan | |
asia-east2 | Hong Kong | |
asia-northeast1 | Tokyo, Japan | |
asia-northeast2 | Osaka, Japan | |
asia-northeast3 | Seoul, South Korea | |
asia-south1 | Mumbai, India | |
asia-south2 | Delhi, India | |
asia-southeast1 | Singapore | |
asia-southeast2 | Jakarta, Indonesia | |
australia-southeast1 | Sydney, Australia | |
australia-southeast2 | Melbourne, Australia |
GCP Region | Location | Private Service Connect | VPC Peering |
|---|---|---|---|
asia-east1 | Taiwan | ✓ | ✓ |
asia-east2 | Hong Kong | ✓ | ✓ |
asia-northeast1 | Tokyo, Japan | ✓ | ✓ |
asia-northeast2 | Osaka, Japan | ✓ | ✓ |
asia-northeast3 | Seoul, South Korea | ✓ | ✓ |
asia-south1 | Mumbai, India | ✓ | ✓ |
asia-south2 | Delhi, India | ✓ | ✓ |
asia-southeast1 | Singapore | ✓ | ✓ |
asia-southeast2 | Jakarta, Indonesia | ✓ | ✓ |
australia-southeast1 | Sydney, Australia | ✓ | ✓ |
australia-southeast2 | Melbourne, Australia | ✓ | ✓ |
GCP Region | Location | Custom Connectors |
|---|---|---|
asia-east1 | Taiwan | |
asia-east2 | Hong Kong | |
asia-northeast1 | Tokyo, Japan | |
asia-northeast2 | Osaka, Japan | |
asia-northeast3 | Seoul, South Korea | |
asia-south1 | Mumbai, India | ✓ |
asia-south2 | Delhi, India | ✓ |
asia-southeast1 | Singapore | ✓ |
asia-southeast2 | Jakarta, Indonesia | |
australia-southeast1 | Sydney, Australia | ✓ |
australia-southeast2 | Melbourne, Australia |
GCP Region | Location | Custom SMT |
|---|---|---|
asia-east1 | Taiwan | |
asia-east2 | Hong Kong | |
asia-northeast1 | Tokyo, Japan | |
asia-northeast2 | Osaka, Japan | |
asia-northeast3 | Seoul, South Korea | |
asia-south1 | Mumbai, India | |
asia-south2 | Delhi, India | |
asia-southeast1 | Singapore | |
asia-southeast2 | Jakarta, Indonesia | |
australia-southeast1 | Sydney, Australia | |
australia-southeast2 | Melbourne, Australia |
GCP Region | Location | Schema Registry |
|---|---|---|
asia-east1 | Taiwan | ✓ |
asia-east2 | Hong Kong | ✓ |
asia-northeast1 | Tokyo, Japan | ✓ |
asia-northeast2 | Osaka, Japan | ✓ |
asia-northeast3 | Seoul, South Korea | ✓ |
asia-south1 | Mumbai, India | ✓ |
asia-south2 | Delhi, India | ✓ |
asia-southeast1 | Singapore | ✓ |
asia-southeast2 | Jakarta, Indonesia | ✓ |
australia-southeast1 | Sydney, Australia | ✓ |
australia-southeast2 | Melbourne, Australia | ✓ |
GCP Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
asia-east1 | Taiwan | ✓ | ||
asia-east2 | Hong Kong | ✓ | ||
asia-northeast1 | Tokyo, Japan | ✓ | ||
asia-northeast2 | Osaka, Japan | ✓ | ||
asia-northeast3 | Seoul, South Korea | ✓ | ||
asia-south1 | Mumbai, India | ✓ | ||
asia-south2 | Delhi, India | ✓ | ||
asia-southeast1 | Singapore | ✓ | ||
asia-southeast2 | Jakarta, Indonesia | ✓ | ||
australia-southeast1 | Sydney, Australia | ✓ | ||
australia-southeast2 | Melbourne, Australia | ✓ |
GCP Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
europe-central2 | Warsaw, Poland | ✓ | ✓ | ✓ | ||
europe-north1 | Finland | ✓ | ✓ | ✓ | ✓ | |
europe-southwest1 | Madrid, Spain | ✓ | ✓ | ✓ | ||
europe-west1 | Belgium | ✓ | ✓ | ✓ | ✓ | |
europe-west2 | London, UK | ✓ | ✓ | ✓ | ✓ | |
europe-west3 | Frankfurt, Germany | ✓ | ✓ | ✓ | ||
europe-west4 | Netherlands | ✓ | ✓ | ✓ | ✓ | |
europe-west6 | Zurich, Switzerland | ✓ | ✓ | ✓ | ||
europe-west8 | Milan, Italy | ✓ | ✓ | ✓ | ✓ | |
europe-west9 | Paris, France | ✓ | ✓ | ✓ | ✓ | |
europe-west12 | Turin, Italy | ✓ | ✓ | ✓ | ✓ |
GCP Region | Location | Flink | Networking |
|---|---|---|---|
europe-central2 | Warsaw, Poland | ||
europe-north1 | Finland | ✓ | Public and private |
europe-southwest1 | Madrid, Spain | ||
europe-west1 | Belgium | ✓ | Public and private |
europe-west2 | London, UK | ✓ | Public and private |
europe-west3 | Frankfurt, Germany | ✓ | Public and private |
europe-west4 | Netherlands | ✓ | Public and private |
europe-west6 | Zurich, Switzerland | ||
europe-west8 | Milan, Italy | ✓ | Public and private |
europe-west9 | Paris, France | ||
europe-west12 | Turin, Italy |
GCP Region | Location | Tableflow |
|---|---|---|
europe-central2 | Warsaw, Poland | |
europe-north1 | Finland | |
europe-southwest1 | Madrid, Spain | |
europe-west1 | Belgium | |
europe-west2 | London, UK | |
europe-west3 | Frankfurt, Germany | |
europe-west4 | Netherlands | |
europe-west6 | Zurich, Switzerland | |
europe-west8 | Milan, Italy | |
europe-west9 | Paris, France | |
europe-west12 | Turin, Italy |
GCP Region | Location | Private Service Connect | VPC Peering |
|---|---|---|---|
europe-central2 | Warsaw, Poland | ✓ | ✓ |
europe-north1 | Finland | ✓ | ✓ |
europe-southwest1 | Madrid, Spain | ✓ | ✓ |
europe-west1 | Belgium | ✓ | ✓ |
europe-west2 | London, UK | ✓ | ✓ |
europe-west3 | Frankfurt, Germany | ✓ | ✓ |
europe-west4 | Netherlands | ✓ | ✓ |
europe-west6 | Zurich, Switzerland | ✓ | ✓ |
europe-west8 | Milan, Italy | ✓ | ✓ |
europe-west9 | Paris, France | ✓ | ✓ |
europe-west12 | Turin, Italy | ✓ | ✓ |
GCP Region | Location | Custom Connectors |
|---|---|---|
europe-central2 | Warsaw, Poland | |
europe-north1 | Finland | |
europe-southwest1 | Madrid, Spain | |
europe-west1 | Belgium | ✓ |
europe-west2 | London, UK | ✓ |
europe-west3 | Frankfurt, Germany | ✓ |
europe-west4 | Netherlands | |
europe-west6 | Zurich, Switzerland | |
europe-west8 | Milan, Italy | |
europe-west9 | Paris, France | |
europe-west12 | Turin, Italy |
GCP Region | Location | Custom SMT |
|---|---|---|
europe-central2 | Warsaw, Poland | |
europe-north1 | Finland | |
europe-southwest1 | Madrid, Spain | |
europe-west1 | Belgium | |
europe-west2 | London, UK | |
europe-west3 | Frankfurt, Germany | |
europe-west4 | Netherlands | |
europe-west6 | Zurich, Switzerland | |
europe-west8 | Milan, Italy | |
europe-west9 | Paris, France | |
europe-west12 | Turin, Italy |
GCP Region | Location | Schema Registry |
|---|---|---|
europe-central2 | Warsaw, Poland | ✓ |
europe-north1 | Finland | ✓ |
europe-southwest1 | Madrid, Spain | ✓ |
europe-west1 | Belgium | ✓ |
europe-west2 | London, UK | ✓ |
europe-west3 | Frankfurt, Germany | ✓ |
europe-west4 | Netherlands | ✓ |
europe-west6 | Zurich, Switzerland | ✓ |
europe-west8 | Milan, Italy | ✓ |
europe-west9 | Paris, France | ✓ |
europe-west12 | Turin, Italy | ✓ |
GCP Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
europe-central2 | Warsaw, Poland | ✓ | ||
europe-north1 | Finland | ✓ | ||
europe-southwest1 | Madrid, Spain | ✓ | ||
europe-west1 | Belgium | ✓ | ||
europe-west2 | London, UK | ✓ | ||
europe-west3 | Frankfurt, Germany | ✓ | ||
europe-west4 | Netherlands | ✓ | ||
europe-west6 | Zurich, Switzerland | ✓ | ||
europe-west8 | Milan, Italy | ✓ | ||
europe-west9 | Paris, France | ✓ | ||
europe-west12 | Turin, Italy | ✓ |
GCP Region | Location | Basic | Standard | Enterprise | Freight | Dedicated |
|---|---|---|---|---|---|---|
me-west1 | Tel Aviv, Israel | ✓ | ✓ | ✓ | ||
me-central1 | Doha, Qatar | ✓ | ✓ | ✓ | ||
me-central2 | Dammam, Saudi Arabia | ✓ | ✓ | ✓ | ✓ |
GCP Region | Location | Flink | Networking |
|---|---|---|---|
me-west1 | Tel Aviv, Israel | ||
me-central1 | Doha, Qatar | ||
me-central2 | Dammam, Saudi Arabia |
GCP Region | Location | Tableflow |
|---|---|---|
me-west1 | Tel Aviv, Israel | |
me-central1 | Doha, Qatar | |
me-central2 | Dammam, Saudi Arabia |
GCP Region | Location | Private Service Connect | VPC Peering |
|---|---|---|---|
me-west1 | Tel Aviv, Israel | ✓ | ✓ |
me-central1 | Doha, Qatar | ✓ | ✓ |
me-central2 | Dammam, Saudi Arabia | ✓ | ✓ |
GCP Region | Location | Custom Connectors |
|---|---|---|
me-west1 | Tel Aviv, Israel | |
me-central1 | Doha, Qatar | |
me-central2 | Dammam, Saudi Arabia |
GCP Region | Location | Custom SMT |
|---|---|---|
me-west1 | Tel Aviv, Israel | |
me-central1 | Doha, Qatar | |
me-central2 | Dammam, Saudi Arabia |
GCP Region | Location | Schema Registry |
|---|---|---|
me-west1 | Tel Aviv, Israel | ✓ |
me-central1 | Doha, Qatar | ✓ |
me-central2 | Dammam, Saudi Arabia | ✓ |
GCP Region | Location | Enterprise | Dedicated | Freight |
|---|---|---|---|---|
me-west1 | Tel Aviv, Israel | ✓ | ||
me-central1 | Doha, Qatar | ✓ | ||
me-central2 | Dammam, Saudi Arabia | ✓ |
Feature | |||||
|---|---|---|---|---|---|
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ | |||
✓ | |||||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | |||
✓ | ✓ | ✓ | ✓ | ||
✓ | |||||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ||||
✓ | ✓ | ✓ | ✓ | ||
✓ | ✓ | ✓ (*) | |||
✓ | |||||
✓ |
* Stream sharing doesn’t support all private networking options.
Feature | Private Service Connect (Inbound) | Private Service Connect (Outbound) | |
|---|---|---|---|
Enterprise cluster | |||
Dedicated cluster type | ✓ | ||
Connect | ✓ | ||
Flink | |||
Schema Registry | |||
Connect with Dedicated Kafka clusters |