Stream Governance Packages, Features, and Limits¶
This page provides an overview of Stream Governance packages, including how to enable or delete them, regions mappings, and feature support available with each package type.
Getting started: enable or upgrade¶
Ready to get started using Stream Governance in your Confluent Cloud environments? Skip to the Quick Start for Schema Management on Confluent Cloud, which begins with explaining how to choose a stream governance package and enable Schema Registry, Stream Catalog, and Stream Lineage.
If you first want to learn more about package options, pricing, features, and how they work, read on! This page goes in depth on Stream Governance packages and features.
Packages¶
Stream Governance is available in two package offerings, which you select at the time you create an environment, or later if you want to upgrade by adding Stream Governance for the first time or switch from Essentials to Advanced:
- Essentials: Starting at $0 cost per hour, provides the fundamentals for getting started; including Schema Registry with 1,000 schemas and 9 cloud regions, stream catalog with auto-technical metadata ingestion, tags metadata, UI, REST API, and most features in stream lineage.
- Advanced: Starting at $1 per hour, provides enterprise-ready controls for data in motion. Includes Schema Registry with 20,000 included schemas and 31 cloud regions, stream catalog with everything in Essentials plus business metadata and GraphQL API, and stream lineage with everything in Essentials plus point in time lineage and searchable lineage graph. The Advanced package also includes support for Data Contracts on Confluent Cloud.
Tip
The schema limits mentioned above apply to the total number of schema versions across all subjects. On Essentials, you can have 1,000 total schema versions across all subjects; on Advanced, you can have 20,000 total schemas across all versions. Therefore; using the Advanced package as an example; it would be possible to have one subject with 20,000 schemas.
Full details on pricing and limits for Confluent Cloud are available on the website at Confluent Cloud pricing for Stream Governance.
Stream Governance packages are enabled per cloud environment, so you can have multiple environments with different package types.
How to enable Schema Registry or upgrade to a Stream Governance package¶
As mentioned above, you can enable always start out using Confluent Cloud without Stream Governance and Schema Registry, and enable/upgrade later. (Just choose “I’ll do it later” when creating a new environment.)
You can add Stream Governance for the first time, or switch from an Essentials to Advanced package for an environment as follows.
Upgrade using the Cloud Console¶
From the Confluent Cloud Console, these options are available for a given environment or feature:
- On the right side panel for an environment under Stream Governance package, choose Enable now to enable Schema Registry for the first time.
- For any feature that requires Stream Governance, select the option on the right panel that is displayed when you hover over the feature to enable Schema Registry for the first time or to upgrade to the needed package level. (For example, Business metadata requires the Advanced package.)
Upgrade using the Confluent CLI¶
If Schema Registry is not enabled for an environment, first enable it with confluent schema-registry cluster enable. For example, this command enables Schema Registry for the currently selected environment to use Google Cloud Platform in the US with the Advanced package:
confluent schema-registry cluster enable --cloud gcp --geo us --package advanced
To upgrade to an environment from Essentials to Advanced, use confluent schema-registry cluster upgrade.
For example, this command upgrades env-abc123 from the Essentials to the Advanced package:
confluent schema-registry cluster upgrade --package advanced --environment env-abc123
Upgrade using the REST API¶
To enable Schema Registry or upgrade from Essentials to Advanced using the Schema Registry Confluent Cloud REST APIs, see the following resources:
Features by package type¶
| Essentials | Advanced |
|---|---|
Stream quality (Schema Registry and validation)
|
Stream quality (Schema Registry and validation)
|
Stream Catalog (data organization and discoverability)
|
Stream Catalog (data organization and discoverability) All existing Essentials features + |
Track Data with Stream Lineage on Confluent Cloud (data origin and tracking)
|
Track Data with Stream Lineage on Confluent Cloud (data origin and tracking) All existing Essentials features + |
| Schema rules for Data Contracts on Confluent Cloud |
Cloud providers and region support¶
When you enable a Stream Governance package, you specify the cloud provider and region where you want the Schema Registry and Stream Catalog services to run, and corresponding metadata to be stored.
Following is a list of the cloud providers and regions available for each of these packages.
Essentials package¶
Amazon Web Services (AWS) regions¶
Following is a list of regions supported for AWS grouped by geographic region.
- Americas: us-east-2 (Ohio)
- Europe: eu-central-1 (Frankfurt)
- Asia Pacific: ap-southeast-2 (Sydney)
Google Cloud Platform (GCP) regions¶
Following is a list of regions supported for GCP grouped by geographic region.
- Americas: us-central1 (Iowa)
- Europe: europe-west3 (Frankfurt)
- Asia Pacific: australia-southeast1 (Sydney)
Microsoft Azure (Azure) regions¶
Following is a list of regions supported for Azure grouped by geographic region.
- Americas: westus2 (Washington)
- Europe: westeurope (Netherlands)
- Asia Pacific: southeastasia (Singapore)
Advanced package¶
Amazon Web Services (AWS) regions¶
Following is a list of regions supported for AWS grouped by geographic region.
- Americas:
- us-east-1 (N. Virginia)
- us-east-2 (Ohio)
- us-west-2 (Oregon)
- ca-central-1 (Canada central)
- Europe:
- eu-central-1 (Frankfurt)
- eu-west-1 (Ireland)
- eu-west-2 (London)
- Asia Pacific:
- ap-south-1 (Mumbai)
- ap-southeast-1 (Singapore)
- ap-southeast-2 (Sydney)
- Africa:
- af-south-1 (Cape Town)
Google Cloud Platform (GCP) regions¶
Following is a list of regions supported for GCP grouped by geographic region.
- Americas:
- us-west4 (Las Vegas)
- us-central1 (Iowa)
- us-east1 (S. Carolina)
- us-east4 (N. Virginia)
- northamerica-northeast1 (Montreal)
- northamerica-northeast2 (Toronto)
- Europe:
- europe-west1 (Belgium)
- europe-west3 (Frankfurt)
- europe-west4 (Netherlands)
- europe-west6 (Zurich)
- Asia Pacific
- asia-southeast1 (Singapore)
- australia-southeast1 (Sydney)
- asia-south2 (Delhi)
Microsoft Azure (Azure) regions¶
Following is a list of regions supported for Azure grouped by geographic region.
- Americas:
- westus2 (Washington)
- eastus (Virginia)
- eastus2 (Virginia)
- centralus (Iowa)
- canadacentral (Canada)
- brazilsouth (Brazil South)
- Europe:
- westeurope (Netherlands)
- northeurope (Ireland)
- uksouth (London)
- switzerlandnorth (Switzerland)
- Middle East:
- uaenorth (Dubai)
- Asia Pacific:
- australiaeast (New South Wales)
- southeastasia (Singapore)
- Africa:
- southafricanorth (Johannesburg)
Schema Registry Regions¶
Confluent Cloud provides built-in Schema Registry regions which map to cloud provider regions. Each region provides a Stream Governance package offering, as shown below.
Built-in Schema Registry regions mapped to AWS regions¶
| ID | Cloud | Region ID | Name | Packages |
|---|---|---|---|---|
| sgreg-35 | AWS | ap-south-1 | Mumbai (ap-south-1) | ADVANCED |
| sgreg-27 | AWS | ap-southeast-1 | Singapore (ap-southeast-1) | ADVANCED |
| sgreg-4 | AWS | ap-southeast-2 | Sydney (ap-southeast-2) | ESSENTIALS, ADVANCED |
| sgreg-29 | AWS | af-south-1 | Cape Town (af-south-1) | ADVANCED |
| sgreg-24 | AWS | ca-central-1 | Canada (ca-central-1) | ADVANCED |
| sgreg-3 | AWS | eu-central-1 | Frankfurt (eu-central-1) | ESSENTIALS, ADVANCED |
| sgreg-25 | AWS | eu-west-1 | Ireland (eu-west-1) | ADVANCED |
| sgreg-26 | AWS | eu-west-2 | London (eu-west-2) | ADVANCED |
| sgreg-22 | AWS | us-east-1 |
|
ADVANCED |
| sgreg-1 | AWS | us-east-2 | Ohio (us-east-2) | ESSENTIALS, ADVANCED |
| sgreg-23 | AWS | us-west-2 | Oregon (us-west-2) | ADVANCED |
Built-in Schema Registry regions mapped to GCP regions¶
| ID | Cloud | Region ID | Name | Packages |
|---|---|---|---|---|
| sgreg-28 | GCP | asia-southeast1 | Singapore (asia-southeast1) | ADVANCED |
| sgreg-31 | GCP | asia-south2 | Delhi (asia-south2) | ADVANCED |
| sgreg-6 | GCP | australia-southeast1 | Sydney (australia-southeast1) | ESSENTIALS, ADVANCED |
| sgreg-20 | GCP | europe-west1 | Belgium (europe-west1) | ADVANCED |
| sgreg-5 | GCP | europe-west3 | Frankfurt (europe-west3) | ESSENTIALS, ADVANCED |
| sgreg-21 | GCP | europe-west4 | Netherlands (europe-west4) | ADVANCED |
| sgreg-36 | GCP | europe-west6 | Zurich (europe-west6) | ADVANCED |
| sgreg-32 | GCP | northamerica-northeast1 | Montreal (northamerica-northeast1) | ADVANCED |
| sgreg-33 | GCP | northamerica-northeast2 | Toronto (northamerica-northeast2) | ADVANCED |
| sgreg-2 | GCP | us-central1 | Iowa (us-central1) | ESSENTIALS, ADVANCED |
| sgreg-19 | GCP | us-east1 |
|
ADVANCED |
| sgreg-18 | GCP | us-east4 |
|
ADVANCED |
| sgreg-17 | GCP | us-west4 | Las Vegas (us-west4) | ADVANCED |
Built-in Schema Registry regions mapped to Azure regions¶
| ID | Cloud | Region ID | Name | Packages |
|---|---|---|---|---|
| sgreg-16 | Azure | australiaeast | New South Wales (australiaeast) | ADVANCED |
| sgreg-30 | Azure | southafricanorth | Johannesburg (southafricanorth) | ADVANCED |
| sgreg-11 | Azure | brazilsouth | Sao Paulo state (brazilsouth) | ADVANCED |
| sgreg-10 | Azure | canadacentral | Toronto (canadacentral) | ADVANCED |
| sgreg-7 | Azure | westus2 | Washington (westus2) | ESSENTIALS, ADVANCED |
| sgreg-38 | Azure | centralus | Iowa (centralus)” | ADVANCED |
| sgreg-12 | Azure | eastus | Virginia (eastus) | ADVANCED |
| sgreg-13 | Azure | eastus2 | Virginia (eastus2)” | ADVANCED |
| sgreg-15 | Azure | uksouth | London (uksouth) | ADVANCED |
| sgreg-14 | Azure | northeurope | Ireland (northeurope) | ADVANCED |
| sgreg-9 | Azure | westeurope | Netherlands (westeurope) | ESSENTIALS, ADVANCED |
| sgreg-34 | Azure | switzerlandnorth | Switzerland (switzerlandnorth) | ADVANCED |
| sgreg-37 | Azure | uaenorth | Dubai (uaenorth) | ADVANCED |
| sgreg-8 | Azure | southeastasia | Singapore (southeastasia) | ESSENTIALS, ADVANCED |
Delete a Stream Governance package¶
You can delete a Stream Governance package from an environment, which deletes the Schema Registry cluster and everything within it, and stops Stream Governance billing.
Stream Governance can subsequently be re-enabled by adding a new package.
To remove an existing package from an environment:
On the Confluent Cloud Console, navigate into the environment from which you want to remove the package.
On the right panel for the environment settings, hover your cursor over the package listed under Stream Governance package to get the trashcan icon.
Click the trashcan, to bring up the Confirm delete dialog.
Fill in the package name, and click Confirm to delete the package.
The package is deleted, which includes removing the Schema Registry cluster and everything within it.