Confluent.license

0 views

Skip to first unread message

Eryn

unread,

Aug 3, 2024, 11:26:22 AM8/3/24

to tiamenmittro

This topic lists the license type that applies to each Confluent or Apache Kafka componentand how to configure the license for manual deployments of Confluent Platformcomponents. For information on how to configure licenses in automateddeployments of Confluent Platform with Confluent for Kubernetes, see Configure licenses with Confluent forKubernetes.

The following table lists the Kafka and Confluent features and whether they are covered under the Enterprise License ,a Community License or an Apache Kafka 2.0 license. For more information, see theCommunity License FAQ.

An enterprise license provides access to all Confluent commercial features for a production environment.An enterprise license is a paid subscription that expires at an interval determined by the subscription contract.The software ceases to function after the license expires. For details, see Renew licenses.

A developer license allows full use of Confluent Platform features free of charge for an indefinite duration.However, the license is limited to a single broker configuration per cluster. The developer licensegives developers the freedom to try the Confluent Platform commercial features available in a non-production setting.

The developer license also accommodates multiple single-broker clusters so that developers can trythe Replicator between those instances, or develop failover applications,for example. Those multiple single-broker clusters share the same license.

A trial (evaluation) license allows a free trial of commercial features in a production setting.Expires after 30 days. The trial license is governed by theConfluent evaluation licenses agreement.The software ceases to function when the license expires. For details, seeRenew licenses.

Each of these components have an option to specify a license key in theirrespective properties file to be evaluated on startup. See below for thecomponent properties files. The components store this key on the_confluent-command topic.

When applying an updated license in Confluent Control Center, you must also provide an updatedlicense key in the Confluent Server configuration file (/etc/kafka/kraft/server.properties).The updated license is evaluated against the current license information thatis present in the _confluent-command topic. If necessary, that originallicense is updated to the newly submitted license, and the updated license isapplied when the brokers restart.

A license is required only when using multiple broker configurations. Configure the parameterconfluent.license in the Kafka server.properties file. For more information, seeConfigure license for rebalancer.

The Confluent Platform commercial connectors can be used on an unlimited basis with the developer license forsingle-broker clusters. Multi-broker clusters can use these commercial connectors for a 30-day trialwithout an enterprise license key. After the trial period expires, Confluent Platform software ceases to function.

You must purchase an enterprise license to continueusing commercial connectors in a multi-broker cluster. If a license is required,configure the confluent.license parameter in the Connect workerconfiguration, or at the individual connector level as described inLicense for Self-Managed Connectors.

When enabled with role-based access control (RBAC) or Kafka REST Security plugins,license clients must be explicitly configured to authenticate to Apache Kafka. For example, if a Kafka REST clienttalks to Kafka over a SASL_SSL enabled listener, the configuration may look like this:

As of Confluent Platform versions 5.2 and later, you are notified of licenseexpiration dates with notificationsfor both trial and enterprise licenses. In addition, the developer licenseprovidesunlimited use of commercial features in a single-broker development environment.Upgrading to the most current version 7.7 is strongly recommended.

Each licensed component requires a valid license key to start up. After thecomponent starts up, it checks the license topic to use the latest valid licensekey. See Configure component licenses for details.

License Manager also logs the license information, including expiration, andadds warning messages to the log 15 days before expiration. Warning messageswill also be shown in Confluent Control Center leading to to a license expiration.

The License Manager checks the license status daily. At 90 days before a licenseexpiration date, a notification messageprominently displays within the Control Center application the number of daysremaining for the license. As the expiration date approaches, notificationsbecome more persistent at the following countdown intervals:

You can request purchase of an enterprise license from within the Control Center.Request a license if you want to upgrade to an enterprise license from a triallicense, or if your trial or enterprise license is about to expire or has expiredand needs to be renewed.

When you apply a valid Enterprise license, it takes effect immediately and does notrequire stopping or restarting services. You can apply a new license key to anenterprise license that is about to expire or has expired.

Applying a license key in the License tab does not update the license stringproperty in the control-center.properties file. However, applying a licensekey in the control-center.properties file does update the license key displayedin the License tab.

Besides using the License tab in the Control Center Administration UI, you can setthe license key in the confluent.license property of the appropriatecontrol-center.properties file on startup. Enter either the license key or apath to the license key file.

Applying a license key in a control-center.properties file updates thelicense key displayed in the License tab UI. Applying a license key in theLicense tab UI does not update the license string property inthe control-center.properties file.

For more details on Control Center configuration options, see Control Center Configuration Reference for Confluent Platform.For more information about restarting Control Center and passing in its properties files,see Control Center Configuration Examples for Confluent Platform.

After disabling License Manager, the License tab in the Control CenterAdministration UI cannot be accessed by any users. Enter the license key usingan Applying a Confluent Platform license in a Control Center properties file.

Before running Replicator, you need to make sure you download Confluent Platform Enterprise from (Replicator is not included in Confluent Open Source). Next extract the contents of the archive. Then, make sure you have two clusters of Kafka Brokers up and running. If you are not sure about that, you can refer to Replicator Quick Start or Confluent Platform Quick Start.

Connect clusters are associated with a cluster of Kafka brokers. The brokers of the Kafka cluster are specified in bootstrap.servers configuration parameter of the Connect workers.If you are configuring a new Connect worker cluster for running Replicator, make sure this parameter contains the destination Kafka brokers cluster.If you are planning on running Replicator on an existing Connect cluster, make sure it is already associated with the destination brokers.

Kafka Connect logging is configured in the file etc/kafka/connect-log4j.properties. By default it just writes to console, but for production deployments you will want to log to a file. Before you start Replicator, add these lines to the connect-log4j.properties file:

Without the license key, you can use Replicator for a 30-day trial period. If you are a Confluent customer, you can contact customer support and ask for a Replicator license key. Then add confluent.license configuration to the Replicator configuration file (see below) followed by the key you recieved from Confluent support.