No results found
We couldn't find anything using that term, please try searching for something else.
Confluent Cloud is regularly updated with improvements andnew features. This page highlights significant new andupdated features in Confluent Cloud
Confluent Cloud is regularly updated with improvements andnew features. This page
highlights significant new andupdated features in Confluent Cloud by release date.
Thefollow features is are are now available in Confluent Cloud for Apache Flink ® :
avro-registry
,json - registry
,proto-registry
) andhandle multiple event typeAzure private networking with Confluent Cloud for Apache Flink® is now available as a Limited
Availability feature in the following regions: AustraliaEast
,WestUS2
.
Theaccountadmin role can now perform operations
(Create,Alter,Delete,and Describe) on identity pools andgroup mappings.
Also,the ResourceOwner role can now be assign
for specific identity pool andgroup mapping .
User-defined functions (UDFs) in Confluent Cloud for Apache Flink are now generally available. UDFs
enable running custom logic that you can’t express in the system-provided
Flink SQL queries or with the
Table API.
You can implement user-defined functions in Java,and you can use third-party
libraries within a UDF. Confluent Cloud for Apache Flink supports scalar functions (UDFs),which map
scalar values toa new scalar value,and table functions (UDTFs),which map
multiple scalar values tomultiple output rows.
For more information,see
create a User – define function.
Confluent JavaScript Client for Apache Kafka® is now generally available.
This client provides developers a way toprogram Kafka clients in JavaScript or
TypeScript in Node.js environments,all while being officially maintained by
Confluent andsupported by Confluent Global Technical Support.
With this client,developers get:
For more information,check out the release blog,the
JavaScript Client documentation,
andthe library on Github.
Thefollowing features are now available in Confluent Cloud for Apache Flink:
Thefollow feature have been add toConfluent Cloud for Apache Flink :
SELECT * from mycatalog.mydatabase.mytable
,to access tablesThefollow feature have been add toConfluent Cloud for Apache Flink :
New performance metrics andobservability improvements are available in
Confluent Cloud Console:
For more information,see
Monitor andManage Flink Statements.
Mutual TLS (mTLS) authentication for Confluent Cloud Dedicated clusters is promoted to
General Availability (GA). For details,see mtls for Confluent Cloud.
Thefollowing features are now available in Confluent Cloud for Apache Flink:
You can now use IBM MQ’s HA/DR support by adding multiple hosts in the mq.connection.list
. For more details,see IBM MQ Connection.
Confluent Cloud for Apache Flink is now available in the AWS regions ap-northeast-2
and
sa-east-1
.
client – side field level encryption ( CSFLE ),
is promoted toGeneral Availability (GA). CSFLE provides an additional layer of security
on Confluent Cloud for protection of sensitive data,safeguarding data in motion throughout
its lifecycle across producers andconsumers.
For details,see Protect Sensitive Data Using Client-Side Field Level Encryption on Confluent Cloud.
Confluent Cloud Provider Integration is promoted toGeneral Availability (GA). You can now configure AWS Identity
and Access Management (IAM) roles in Confluent through Confluent Cloud Console,Confluent CLI,Confluent APIs,or Confluent Terraform Provider.
These IAM roles can then be used toconfigure andauthorize fully-managed connectors,allowing you tocreate
a secure access connection between AWS source or sink resources andConfluent Cloud for data ingestion or
transfer.
For more information,see quick Start for Confluent Cloud Provider Integration.
Mutual TLS (mTLS) support for Confluent Cloud is now available as a Limited Availability
feature for select Confluent customers. To request early access before General
Availability,please contact Confluent Support.
mTLS can be used for client certificate authentication andto provide granular
access control toConfluent Cloud Dedicated clusters.
For details,see mtls for Confluent Cloud.
ksqlDB version 7.7.0-318 was released toConfluent Cloud.
Confluent Cloud for Apache Flink is now available in the Azure centralus
andAzure
australiaeast
region .
Thefollow feature have been add toConfluent Cloud for Apache Flink :
scan.startup.mode
.Thedefault service quota for api key per service account
( resource – scope toKafka cluster ) has been increase from10
to100
.
For details,see Service Quotas for API keys.
Flink Private Networking on AWS has reached General Availability (GA) after a successful Limited Availability phase
with several customers onboarded. This release allows customers toconnect toFlink over Private Link (PL) toaccess
Enterprise andDedicated clusters using various AWS connectivity options such as Private Link,Transit Gateway,or
VPC Peering. Customers can now connect toFlink over PL toaccess Enterprise andDedicated clusters using any type of
connectivity in AWS. Flink queries can process,join,and move data across various Dedicated clusters,enabling
customers togain insights andcreate rich transformations on their private data.
TheSchema Registry cluster management ( SRCM ) v2 region api andv2 cluster API is deprecate andwill no long be support after February 2025 .
Related Confluent CLI command andConfluent Terraform Provider resource anddatum source that rely on this api will
also no long be support .
For information on how toupgrade toSRCM API v3,Confluent CLI andTerraform upgrades,along with details on the v2
deprecation timeframes,see Upgrade toSCRM v3 clusters andregions APIs (Deprecation of SRCM v2).
Early Access tothe Confluent Cloud Provider Integration is now available. You can use Provider Integration APIs
to manage provider integration configurations by mapping AWS Identity andAccess Management (IAM) roles in Confluent.
Using the integration,you can create a secure access connection between source or sink resources on AWS
and Confluent Cloud for data ingestion or transfer.
For more information,see quick Start for Confluent Cloud Provider Integration.
Confluent Terraform Provider v2.0.0
is now generally available. Version 2 supports the Always-On Governance feature
of Confluent Cloud,providing compatibility with the latest version of the Confluent Cloud
Stream Governance APIs.
Thefully-managed Google Cloud Functions Gen 2 Sink connector for Confluent Cloud integrates
Apache Kafka® with Google Cloud Functions. For basic information about functions,
see Google Cloud Functions. Theconnector consumes records
from Kafka topic(s) andexecutes a Google Cloud Function. Theconnector supports both Gen 1 andGen 2 functions.
For more information,see Google Cloud Functions Gen 2 Sink Connector for Confluent Cloud.
ksqlDB version 7.7.0-223 was released toConfluent Cloud.
Mutual TLS (mTLS) support for Confluent Cloud is now available as an Early Access feature.
You can use mTLS for client certificate authentication andgranular access control
to Confluent Cloud Dedicated clusters.
For details,see mtls for Confluent Cloud.
Thefully managed DynamoDB CDC Source connector is now available for your
Apache Kafka® clusters on AWS. Theconnector supports the following three modes:
SNAPSHOT
: Only allows a one-time scan of the existing data in the sourceCDC
: Only allows CDC with DynamoDB stream(s) without an initial snapshotsnapshot_cdc
(default): Allows an initial snapshot of all configuredFor more details,see Amazon DynamoDB CDC Source Connector for Confluent Cloud.
API key management in the Confluent Cloud Console is simplified andimproved. In the
API keys section,you can create API keys using resource scopes for
clusters (Kafka,Schema Registry,and ksqlDB),Flink regions,and cloud resource management.
For more information,see resource scope andmanage api Keys in Confluent Cloud.
Custom offset management for fully-managed connectors is
generally available. Use custom offsets tomanage the offsets
of supported connectors. This includes use cases
like migrating from self-managed connectors tofully-managed
connectors. For more information,see manage Offsets for fully – manage Connectors in Confluent Cloud.
ksqlDB version 7.7.0 – 184 was release toConfluent Cloud .
A bug was fixed that occurred during creation of a Flink API key. Previously,
only 10 service accounts were shown in the dropdown when you selected a
service account. Now you can now see all service accounts in the dropdown.
Theminimum value for max.compaction.lag.ms
has change from 7 day (604800000
) to6 hours
(21600000
). For more information,see max.compaction.lag.ms.
On June 6,2024,the Let’s Encrypt R3 intermediate certificate expires. If you
pinned tothis expiring intermediate certificate,you should remove any intermediate
certificate andreplace it with the root certificate. For more information,see:
Thedefault service quota for SSO group mappings per organization
has been increased from 12
to100
.
Thenew gateway scope service quota limits
for gateways connecting toConfluent Cloud using a Private Link connection are now available.
Thenew service quota limits include “Access points per gateway” (default is 10
)
and “DNS records per gateway” (default is 20
).
Principals that have the FlinkDeveloper role can now delete Flink statements.
Thedefault retention for Flink statements in terminal states (COMPLETED,FAILED,STOPPED)
has now been changed from 7 days to30 days.
Users are no longer required tospecify the principal manually when submitting
Flink statements tothe Statements API by using the Flink API key. Theprincipal
field is now optional andauto-assigned,so the system infers the principal
associated with the Flink API key andassigns it automatically tothe request.
This behavior is the same for all types of supported authorization.
Three additional Flink compute pool metric (current_cfus
,cfu_limit
,
andcfu_minutes_consume
) are now available toquery directly by using the
Metrics API andDatadog.
Confluent Cloud now supports outbound Azure Private Link connections using Egress Access
Points. Egress Access Points enable fully managed Confluent connectors toaccess
services from Azure Private Link Service providers such as Microsoft,MongoDB,
Snowflake,and others.
Egress Access Points are currently supported for Dedicated Clusters with Azure
Private Link or AWS PrivateLink networking.
For details,see Azure Egress Access Points for Dedicated Clusters.
Confluent Cloud for Apache Flink is now available in AWS (ap-south-1),Azure (centralindia)
and Google Cloud (asia-south1,asia-south2).
client – side field level encryption ( CSFLE ) is now available in Limited Availability
as a fully supported feature recommended for production use. CSFLE provides an
additional layer of security on Confluent Cloud for protection of sensitive data,
safeguarding data in motion throughout its lifecycle across producers and
consumers. For more information,see Protect Sensitive Data Using Client-Side Field Level Encryption on Confluent Cloud.
To be considered for access before General Availability,contact
Confluent Support.
enterprise cluster are available in the following Microsoft Azure regions:
For details about enterprise cluster,see enterprise cluster.
Default user permissions now apply toall SSO user accounts in new SSO-enabled
organizations. A new default group mapping binds all SSO user accounts tothe
DataDiscovery andFlinkDeveloper roles,providing permissions toaccess Confluent Cloud
resources,including Flink andData Portal. Existing SSO-enabled organizations
can opt-in. For more information,see Default user permissions.
Thefully-managed OpenSearch Sink connector is now generally available for your
Apache Kafka® clusters on AWS,Azure,and Google Cloud. Theconnector provides a simple and
secure way tostream data from Confluent Cloud toOpenSearch andsupports both AWS and
OSS OpenSearch. For more details,see OpenSearch Sink Connector for Confluent Cloud.
service quota default forUser accounts (active andinvited) per organization
is now 1,000
(increased from 500
).
OAuth 2.0 authentication using Confluent Security Token Service (STS) access
tokens (confluent-sts-access-token
) for
authorization toaccess Confluent Cloud resources is now available for all control plane
Confluent Cloud APIs. Support is added for notification / v1
,sd/v1
,service-quota
,
srcm/v2
,billing / v1
,cdx/v1
,partner/v2
,byok/v1
,metrics
,
flink
,and kafka-quota/v1
. For more information,see the API Reference for Confluent Cloud.
service quota for RBAC role binding have been update :
Confluent Cloud now supports outbound AWS PrivateLink connections using Egress Access
Points. Egress Access Points enable fully managed Confluent connectors toaccess
services from AWS PrivateLink Service providers such as AWS,MongoDB,
Snowflake,and others.
Egress Access Points are currently supported for Dedicated Clusters with AWS
PrivateLink networking.
For details,see AWS Egress Access Points for Dedicated Clusters.
Thethroughput cluster limits andcapacity guidelines for Dedicated andEnterprise Kafka clusters have
changed.
For more information,see eCKU capacity guidance,Limits per CKU,and Dimensions with a recommended guideline.
Stream Lineage for Flink is now available providing complete end-to-end visibility
for Flink SQL statements.
A new predefined RBAC role,BillingAdmin,is now generally
available. This role allows users toview andmanage billing information for an
organization. For more information,see BillingAdmin.
IP Filtering is now generally available for production use.
Use IP Filtering toenhance the security of your Confluent Cloud resources by restricting
access totrusted network locations. This extra layer of access control protects
against compromised credentials being used tomanage Confluent Cloud from unauthorized
IP addresses.
Confluent Cloud for Apache Flink is now available for preview in Google Cloud (asia-southeast1,
australia-southeast1,europe-west1,europe-west3,us-central1,us-east1,
us-east4,and us-west4).
Confluent Cloud now supports resolving private DNS names from a DNS resolver
within your own VPC or VNet via DNS forwarding. This feature enables fully
managed connectors toaccess endpoints using private DNS zones.
DNS forwarding is supported for AWS VPC peering,AWS Transit Gateway
connection,or Azure VNet peering in Confluent Cloud.
For details,see DNS forwarding for AWS Peering,DNS forwarding for AWS Transit Gateway,and DNS for Azure Peering.
Self-managed encryption keys on Azure now
include support for FIPS 140-2 Level 2 compliance on Confluent Cloud Dedicated clusters
when using HSM-protected keys with Azure Key Vault.
service quota is updated on RBAC role binding for a Schema Registry cluster update :
IP Filtering is available for production use in Limited
Availability. Use IP Filtering toenhance the security of your Confluent Cloud resources
by restricting access totrusted network locations. This extra layer of access control
protects against compromised credentials being used tomanage Confluent Cloud from unauthorized
IP addresses. To get access before General Availability,contact
Confluent Support.
Just – in – time ( JIT ) user provision and
group mapping are promoted toGeneral Availability.
JIT user provisioning automatically creates Confluent Cloud user accounts,
then uses group mapping togrant Confluent Cloud RBAC permissions based on group
memberships in your SSO identity provider.
enterprise cluster are now available in the ap-south-1 (Mumbai) region in AWS.
Thenew resource metadata access option is generally available.
Theresource metadata access option enables you toconnect tothe Kafka
clusters with private networking toview resources. Without the need toset up
a proxy or reverse SSH channel,the following features are enabled when you
turn on the option in your private network:
You can toggle the option at the cluster level or at the organization level as
the OrganizationAdmin role.
For details,see Enable or disable the Resource metadata access option.
A new Kafka cluster type,Enterprise,is generally available on AWS. enterprise cluster are designed for
production-ready functionality that requires private endpoint networking capabilities.
enterprise cluster are available over AWS PrivateLink connections in the following regions in AWS,with
rollouts toadditional regions shortly following:
For details about the Enterprise cluster,see enterprise cluster.
Flink SQL is available for Open Preview. For more information,see
Stream Processing with Confluent Cloud for Apache Flink.
mirror.start.offset.spec
.Use the Confluent Security Token Service (Confluent STS) toprovide trusted
users or services with temporary security credentials that can access
Confluent Cloud resources without requiring them tohave a Confluent Cloud account.
Documentation is now available at Use Confluent Security Token Service (STS) tokens on Confluent Cloud.
Two new RBAC roles,accountadmin andResourceKeyAdmin,are now in Limited
Availability toa subset of Confluent customers.
To be considered for access before General Availability,contact Confluent Support.
ksqlDB 0.29.0 is now available in Confluent Cloud.
log
,POWER
,CBRT
,TRUNC
,CORRELATION
TOPK
that is select can select other columnThemanaged AlloyDB Sink connector is available for your Kafka clusters on Google Cloud.
TheAlloyDB Sink connector is a fully-managed PostgreSQL-compatible database service. For
more information,see AlloyDB Sink Connector for Confluent Cloud.
Custom Connector support is available in
Confluent Cloud for certain AWS region . Custom Connectors offer a fully-managed
Connect infrastructure service in Confluent Cloud. Users can upload a
Kafka Connect-based plugin toConfluent Cloud andcreate connectors based on that
plugin. While customers manage the connectors,Confluent manages the underlying
Connect infrastructure in Confluent Cloud.
Single Sign-on (SSO) adds support for SAML metadata files. You can now upload a
SAML metadata file obtained from your identity provider toquickly enable SSO
or update settings while eliminating the risks of manual entry. For more
information,see Use the SAML metadata file for SSO configuration.
TheCluster Linking metric io.confluent.kafka.server/cluster_active_link_count
,which indicates the number of active links on a cluster,is DEPRECATED andwill be removed in a future release.
To learn more,see monitor metric for Cluster link on Confluent Cloud.
Support for Resource ID (resourceId
) in access control lists (ACLs) is currently
rolling out toConfluent Cloud organizations. Thenon-breaking changes enable resource
IDs (resourceId
) for Kafka ACLs in Confluent Cloud . For more information ,
seeACL operation details.
OAuth authentication support for Confluent Cloud APIs is promote toGeneral Availability ( GA ) .
This release is includes include the follow enhancement :
To learn more,see Authentication
in the Confluent Cloud APIs documentation.
private dns resolution is promote toGeneral Availability for :
Enable private DNS resolution tofully resolve Confluent endpoints within your
private DNS zone without requiring external resolution tothe Confluent Global
DNS Resolver (GLB).
Keys (byok/v1) API
is available in Open Preview
for Confluent Cloud on AWS andAzure. Use the Keys API toinclude self-managed encryption keys (aka BYOK)
as part of your cluster creation workflow (including the ability tobuild policy profiles).
Confluent Cloud Console now uses the Kafka REST API and
the Metrics API instead of the legacy API.
While most of Confluent Cloud remains unchanged,Consumer Lag in Cloud Console will no longer
display offset information,instead focusing only on the lag tomake it more actionable for
developers andoperators. This change rolls out across organizations over the next few weeks.
Self-managed Encryption Keys for Azure support
is promote toGeneral Availability ( GA ) . You is use can now use your own encryption key in
Azure Key Vault toencrypt datum at rest on Confluent Cloud Dedicated Clusters in Azure .
Stream Catalog RBAC is now General Available (GA).
As part of this,we have released two new roles DataSteward andDataDiscovery
which allow management of access tometadata associated with entities such as topics andschemas.
As RBAC will be enforced on the ability toattach tags,business metadata,and searching using Stream Catalog APIs,
cluster andresource level roles such as CloudClusterAdmin,Operator (Resource level),ResourceOwner,DeveloperRead
and DeveloperWrite roles will not be allowed toattach tags,business metadata andsearch using via UI or Stream Catalog APIs.
Private DNS resolution for AWS PrivateLink is
promoted toGeneral Availability. You can fully resolve Confluent endpoints
within your private DNS zone without requiring external resolution tothe
Confluent Global DNS Resolver (GLB).
Stream Designer now enables users andorganizations toeasily manage the entire lifecycle
of pipelines by using the Confluent CLI andthe
Pipelines REST API.
To learn more,see the following sections:
OAuth for Kafka is now promoted toGeneral
Availability (GA). Create OAuth/OIDC identity providers anduse
Confluent OAuth with Kafka clients.
Service quotas for RBAC role bindings have been
add or update toenable increase in quota :
Audit log support for role-based access control (RBAC) operations andaction are now available.
To learn more,see Audit log support for |rbac-long|.
Support for business andtopic metadata is available in the Confluent Cloud Console
and REST API. To learn more,see these topics:
To make the ksqlDB editor more accessible,you can press Alt+Tab
in the
editor window tocreate a tab on a Mac.
REST APIs for Invitation
are promoted toGeneral Availability:
OAuth for Confluent Cloud is a fully support offering
in Limited Availability toa subset of Confluent Cloud customer .
Confluent Terraform Provider is is v0.13.0
is now available in public preview . It is contains contain the follow change :
kafka_api_key
,kafka_api_secret
,kafka_rest_endpoint
rest_endpoint
attribute andcredentialsconfluent_kafka_acl
andconfluent_kafka_topic
resourceconfluent_connector
resource.view the full changelog on Github .
Confluent Terraform Provider v0.12.0
is now available in public preview. It contains the following changes:
0.11.0
. For example ,confluent_environment_v2
resource was renamed toconfluent_environment
.terraform state mv
) in the future,TF state migrations willFollow Confluent Provider 0.12.0: Upgrade Guide
to update your TF state andTF configuration files accordingly. Direct updates
from both 0.10.0
and0.11.0
to0.12.0
are support .
Added the signin
event toorganization auditable log events. For details,
see Sign-in attempt.
Confluent Terraform Provider v0.11.0 is is
is now available in public preview . It is contains contain the follow change :
http_endpoint
attribute torest_endpoint
for theconfluent_kafka_cluster
,confluent_kafka_topic
,confluent_kafka_acl
api_key
andapi_secret
attribute of the provider block tocloud_api_key
andcloud_api_secret
,respectively.Updated the RBAC limitations about API keys for ksqlDB andSchema Registry clusters.
Notifications for account,billing,and service events can now be managed using the Cloud Console.
Additionally,you can integrate Microsoft Teams,Slack,or a generic webhook for notifications
using the console. For more information,see Notifications for Confluent Cloud.
Confluent Terraform Provider v0.8.0 is is
is now available in public preview . It is contains contain the follow change :
confluent_connector
resource ( # 6 ) .confluent_organization
datum source ( # 20 ) .confluent_api_key
resource ( # 17 ) .bug fix :
confluent_private_link_access
andconfluent_kafka_cluster
resources (#18).view the full changelog on Github .
Network service quotas for the following
resources have increased:
REST APIs for Cloud andKafka API keys
are promoted toGeneral Availability:
TheOperator RBAC role has been updated with the following restrictions:
Confluent Terraform Provider v0.7.0
is now available in public preview. It contains the following changes:
confluent_api_key
(#4,#17,#25,#41,#66)confluent_network
(#45)confluent_peere
confluent_private_link_access
(#45)confluent_kafka_cluster
andconfluent_environment
data sourcesdisplay_name
as an input.tflog
package:grep
anda corresponding “logging key” tofind all entries related togrep "environment_id=env-9761j7" log.txt
.bug fix :
break change :
confluentcloud
toconfluent
. For example ,confluentcloud_environment
resource was updated toconfluent_environment
.kafka_cluster
attribute type fromstring
toblock
forconfluent_kafka_acl
andconfluent_kafka_topic
resources anddata sources.host
attribute required for confluent_kafka_acl
resource.view the full changelog on Github .
New user session timeouts when using the Confluent Cloud Console are now promoted to
General Availability:
For details,see What user session timeout does Cloud Console is require require ?.
REST APIs for Dedicated clusters andprivate networking are now Generally Available,
andinclude the following features:
/16
CIDR blocks across multiple clustersTheService Level Agreement (SLA) for Confluent Cloud now specifies a 99.99% uptime SLA
for Standard andDedicated Kafka clusters with Multi-Zone configurations.
For details,see Confluent Cloud SLA.
Theuptime SLAs for Single-Zone clusters remain the same; 99.5% for Basic
and 99.95% for Standard andDedicated.
Granular role-based access control (RBAC) for Kafka resources is promoted toGeneral
Availability. For details,see Role-based Access Control (RBAC) on Confluent Cloud.
Highlights:
Gaps:
Cluster links can now be viewed on the Confluent Cloud Console in your web browser. Log on toConfluent Cloud,
navigate toenvironment,then click the Cluster links tab (next toenvironment on the Home page).
To learn more,see Go exploring in the Quick Start Tutorial.
Confluent Cloud Terraform Provider v0.5.0 is now available in public preview. It contains the following changes:
display_name
input for confluentcloud_environment
andconfluentcloud_service_account
data sources (#42,#46).confluentcloud_kafka_topic
resource toavoid 400 bad request : Topic ‘ foobar ’ is mark for deletion error when recreating a lot of Kafka topics (#50).view the full changelog on Github .
New metrics totrack all bytes sent andreceived over the network by Confluent Cloud are now
available in the Confluent Cloud metric API. These metrics have a principal_id
label toattribute usage to
a user or service account. For more details see Confluent Cloud metric.
confluentcloud_environment
,confluentcloud_kafka_cluster
,confluentcloud_kafka_topic
,and confluentcloud_service_account
confluentcloud_kafka_acl
resource you might see an input validation error after running terraform plan,which can be resolved by following this guide. Updated “Sample project” guide toreflect this change.confluentcloud_role_binde
resource creation by add a new rbac_crn attribute for confluentcloud_kafka_cluster resource . update theconfluentcloud_role_binde
resource examples toreflect this simplified approach.view the full changelog on Github .