Supported Apache Kafka versions
Amazon Managed Streaming for Apache Kafka (Amazon MSK) supports the following Apache Kafka and Amazon MSK versions. The Apache Kafka community provides approximately 12 months of support for a version after its release date. For more details check the Apache Kafka EOL (end of life) policy
Apache Kafka version | MSK release date | End of support date |
---|---|---|
1.1.1 |
-- | 2024-06-05 |
2.1.0 |
-- | 2024-06-05 |
2.2.1 |
2019-07-31 | 2024-06-08 |
2.3.1 |
2019-12-19 | 2024-06-08 |
2.4.1 |
2020-04-02 | 2024-06-08 |
2.4.1.1 |
2020-09-09 | 2024-06-08 |
2.5.1 |
2020-09-30 | 2024-06-08 |
2.6.0 |
2020-10-21 | 2024-09-11 |
2.6.1 |
2021-01-19 | 2024-09-11 |
2.6.2 |
2021-04-29 | 2024-09-11 |
2.6.3 |
2021-12-21 | 2024-09-11 |
2.7.0 |
2020-12-29 | 2024-09-11 |
2.7.1 |
2021-05-25 | 2024-09-11 |
2.7.2 |
2021-12-21 | 2024-09-11 |
2.8.0 |
-- | 2024-09-11 |
2.8.1 |
2022-10-28 | 2024-09-11 |
2.8.2-tiered |
2022-10-28 | 2025-01-14 |
3.1.1 |
2022-06-22 | 2024-09-11 |
3.2.0 |
2022-06-22 | 2024-09-11 |
3.3.1 |
2022-10-26 | 2024-09-11 |
3.3.2 |
2023-03-02 | 2024-09-11 |
3.4.0 |
2023-05-04 | 2025-06-17 |
3.5.1 (recommended) |
2023-09-26 | -- |
3.6.0 |
2023-11-16 | -- |
3.7.x |
2024-05-29 | -- |
For more information on Amazon MSK version support policy, see Amazon MSK version support policy.
Apache Kafka version 3.7.x (with production-ready tiered storage)
Apache Kafka version 3.7.x on MSK includes support for Apache Kafka version 3.7.0. You can create clusters or upgrade existing clusters to use the new 3.7.x version. With this change in version naming, you no longer have to adopt newer patch fix versions such as 3.7.1 when they are released by the Apache Kafka community. Amazon MSK will automatically update 3.7.x to support future patch versions once they become available. This allows you to benefit from the security and bug fixes available through patch fix versions without triggering a version upgrade. These patch fix versions released by Apache Kafka don't break version compatibility and you can benefit from the new patch fix versions without worrying about read or write errors for your client applications. Please make sure your infrastructure automation tools, such as CloudFormation, are updated to account for this change in version naming.
Amazon MSK now supports KRaft mode (Apache Kafka Raft) in Apache Kafka version 3.7.x. On Amazon MSK, like with ZooKeeper nodes, KRaft controllers are included at no additional cost to you, and require no additional setup or management from you. You can now create clusters in either KRaft mode or ZooKeeper mode on Apache Kafka version 3.7.x. In Kraft mode, you can add up to 60 brokers to host more partitions per-cluster, without requesting a limit increase, compared to the 30-broker quota on Zookeeper-based clusters. To learn more about KRaft on MSK, see KRaft mode.
Apache Kafka version 3.7.x also includes several bug fixes and new features that
improve performance. Key improvements include leader discovery optimizations for
clients and log segment flush optimization options. For a complete list of
improvements and bug fixes, see the Apache Kafka release notes for 3.7.0
Apache Kafka version 3.6.0 (with production-ready tiered storage)
For information about Apache Kafka version 3.6.0 (with production-ready tiered
storage), see its release
notes
Amazon MSK will continue to use and manage Zookeeper for quorum management in this release for stability.
Amazon MSK version 3.5.1
Amazon Managed Streaming for Apache Kafka (Amazon MSK) now supports Apache Kafka version 3.5.1 for new and existing clusters. Apache Kafka 3.5.1 includes several bug fixes and new features that improve performance. Key features include the introduction of new rack-aware partition assignment for consumers. Amazon MSK will continue to use and manage Zookeeper for quorum management in this release. For a complete list of improvements and bug fixes, see the Apache Kafka release notes for 3.5.1.
For information about Apache Kafka version 3.5.1, see its release
notes
Amazon MSK version 3.4.0
Amazon Managed Streaming for Apache Kafka (Amazon MSK) now supports Apache Kafka version 3.4.0 for new and existing clusters. Apache Kafka 3.4.0 includes several bug fixes and new features that improve performance. Key features include a fix to improve stability to fetch from the closest replica. Amazon MSK will continue to use and manage Zookeeper for quorum management in this release. For a complete list of improvements and bug fixes, see the Apache Kafka release notes for 3.4.0.
For information about Apache Kafka version 3.4.0, see its release
notes
Amazon MSK version 3.3.2
Amazon Managed Streaming for Apache Kafka (Amazon MSK) now supports Apache Kafka version 3.3.2 for new and existing clusters. Apache Kafka 3.3.2 includes several bug fixes and new features that improve performance. Key features include a fix to improve stability to fetch from the closest replica. Amazon MSK will continue to use and manage Zookeeper for quorum management in this release. For a complete list of improvements and bug fixes, see the Apache Kafka release notes for 3.3.2.
For information about Apache Kafka version 3.3.2, see its release
notes
Amazon MSK version 3.3.1
Amazon Managed Streaming for Apache Kafka (Amazon MSK) now supports Apache Kafka version 3.3.1 for new and existing clusters. Apache Kafka 3.3.1 includes several bug fixes and new features that improve performance. Some of the key features include enhancements to metrics and partitioner. Amazon MSK will continue to use and manage Zookeeper for quorum management in this release for stability. For a complete list of improvements and bug fixes, see the Apache Kafka release notes for 3.3.1.
For information about Apache Kafka version 3.3.1, see its release
notes
Amazon MSK version 3.1.1
Amazon Managed Streaming for Apache Kafka (Amazon MSK) now supports Apache Kafka version 3.1.1 and 3.2.0 for new and existing clusters. Apache Kafka 3.1.1 and Apache Kafka 3.2.0 includes several bug fixes and new features that improve performance. Some of the key features include enhancements to metrics and the use of topic IDs. MSK will continue to use and manage Zookeeper for quorum management in this release for stability. For a complete list of improvements and bug fixes, see the Apache Kafka release notes for 3.1.1 and 3.2.0.
For information about Apache Kafka version 3.1.1 and 3.2.0, see its 3.2.0 release notes
Amazon MSK tiered storage version 2.8.2.tiered
This release is an Amazon MSK-only version of Apache Kafka version 2.8.2, and is compatible with open source Apache Kafka clients.
The 2.8.2.tiered release contains tiered storage functionality that is compatible with APIs introduced in KIP-405 for Apache Kafka
Apache Kafka version 2.5.1
Apache Kafka version 2.5.1 includes several bug fixes and new features, including encryption in-transit for Apache ZooKeeper and administration clients. Amazon MSK provides TLS ZooKeeper endpoints, which you can query with the DescribeCluster operation.
The output of the
DescribeCluster operation includes the ZookeeperConnectStringTls
node, which lists
the TLS zookeeper endpoints.
The following example shows the ZookeeperConnectStringTls
node of the response for the
DescribeCluster
operation:
"ZookeeperConnectStringTls": "z-3.awskafkatutorialc.abcd123.c3.kafka.us-east-1.amazonaws.com:2182,z-2.awskafkatutorialc.abcd123.c3.kafka.us-east-1.amazonaws.com:2182,z-1.awskafkatutorialc.abcd123.c3.kafka.us-east-1.amazonaws.com:2182"
For information about using TLS encryption with zookeeper, see Using TLS security with Apache ZooKeeper.
For more information about Apache Kafka version 2.5.1, see its release
notes
Amazon MSK bug-fix version 2.4.1.1
This release is an Amazon MSK-only bug-fix version of Apache Kafka version 2.4.1.
This bug-fix release contains
a fix for KAFKA-9752PreparingRebalance
state. This issue affects clusters running Apache
Kafka versions 2.3.1 and 2.4.1. This release contains a community-produced
fix that is available in Apache Kafka version 2.5.0.
Note
Amazon MSK clusters running version 2.4.1.1 are compatible with any Apache Kafka client that is compatible with Apache Kafka version 2.4.1.
We recommend that you use MSK bug-fix version 2.4.1.1 for new Amazon MSK clusters if you prefer to use Apache Kafka 2.4.1. You can update existing clusters running Apache Kafka version 2.4.1 to this version to incorporate this fix. For information about upgrading an existing cluster, see Update the Apache Kafka version.
To work around this issue without upgrading the cluster to version 2.4.1.1, see the Consumer group stuck in PreparingRebalance state section of the Troubleshoot your Amazon MSK cluster guide.
Apache Kafka version 2.4.1 (use 2.4.1.1 instead)
Note
You can no longer create an MSK cluster with Apache Kafka version 2.4.1. Instead, you can use Amazon MSK bug-fix version 2.4.1.1 with clients compatible with Apache Kafka version 2.4.1. And if you already have an MSK cluster with Apache Kafka version 2.4.1, we recommend you update it to use Apache Kafka version 2.4.1.1 instead.
KIP-392 is one of the key Kafka Improvement Proposals that are included in the 2.4.1
release of Apache Kafka. This improvement allows consumers to fetch from the closest
replica. To use this feature, set client.rack
in the consumer properties to
the ID of the consumer's Availability Zone. An example AZ ID is use1-az1
.
Amazon MSK sets broker.rack
to the IDs of the Availability Zones of the brokers.
You must also set the replica.selector.class
configuration property to
org.apache.kafka.common.replica.RackAwareReplicaSelector
, which is an
implementation of rack awareness provided by Apache Kafka.
When you use this version of Apache Kafka, the metrics in the
PER_TOPIC_PER_BROKER
monitoring level appear only after their values
become nonzero for the first time. For more information about this, see PER_TOPIC_PER_BROKER Level
monitoring.
For information about how to find Availability Zone IDs, see AZ IDs for Your Resource in the AWS Resource Access Manager user guide.
For information about setting configuration properties, see Amazon MSK Provisioned configuration.
For more information about KIP-392, see Allow Consumers to Fetch from Closest Replica
For more information about Apache Kafka version 2.4.1, see its release
notes