Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account

Create an MSK Provisioned cluster using the AWS Management Console

PDF
RSS
Focus mode
Create an MSK Provisioned cluster using the AWS Management Console - Amazon Managed Streaming for Apache Kafka

This process describes the common task of creating an MSK Provisioned cluster using custom create options in the AWS Management Console. You can select other options in the AWS Management Console to create a serverless cluster.

  1. Open the Amazon MSK console at https://console.aws.amazon.com/msk/home?region=us-east-1#/home/.

  2. Choose Create cluster.

  3. For Cluster creation method, choose Custom create.

  4. Specify a Cluster name that is unique and no more than 64 characters.

  5. For General cluster properties, choose Provisioned as the Cluster type.

  6. Select the Apache Kafka version to run on the brokers. To see a comparison of Amazon MSK features that are supported by each Apache Kafka version, click View version compatibility.

  7. Choose either Express brokers or Standard brokers broker type.

  8. Select a broker size to use for the cluster based on the cluster’s compute, memory, and storage needs. See Amazon MSK broker types,

  9. Select the Number of zones across which brokers are distributed. Express brokers require 3 Availability Zones for higher availability.

  10. Specify the number of brokers you want MSK to create in each Availability Zone. The minimum is one broker per Availability Zone and the maximum is 30 brokers per cluster for ZooKeeper-based clusters and 60 brokers per cluster for KRaft-based clusters.

  11. (Standard brokers only) Select the initial amount of Storage you want your cluster to have. You can't decrease storage capacity after you create the cluster. You don't need to manage storage for Express brokers.

  12. (Standard brokers only) Depending on the broker size (instance size) you selected, you can specify Provisioned storage throughput per broker. To enable this option, choose broker size (instance size) kafka.m5.4xlarge or larger for x86, and kafka.m7g.2xlarge or larger for Graviton-based instances. See Provision storage throughput for Standard brokers in a Amazon MSK cluster.

  13. (Standard brokers only) Select a Cluster storage mode option, either EBS storage only or tiered storage and EBS storage. Express brokers don't require you to manage storage.

  14. If you want to create and use a custom Cluster configuration (or if you already have a cluster configuration saved), choose a configuration. Otherwise, you can create the cluster using the Amazon MSK default cluster configuration. For information about Amazon MSK configurations, see Amazon MSK Provisioned configuration.

  15. Select Next.

  16. For Networking settings, choose the VPC you want to use for the cluster.

  17. Based on the Number of zones you previously selected, specify the Availability Zones and subnets where brokers will deploy. For Standard brokers in the US West (N. California) Region, you need two subnets in two different Availability Zones. In all other Regions where Amazon MSK is available, you can specify either two or three subnets. Your subnets must all be in different Availability Zones. For Express brokers, you need three subnets in three different Availability Zones. When you create an MSK Provisioned cluster, MSK distributes the broker nodes evenly over the subnets that you specify.

  18. You can select one or more security groups that you want to give access to your cluster (for example, the security groups of client machines). If you specify security groups that are shared with you, you must ensure that you have permissions to use them. Specifically, you need the ec2:DescribeSecurityGroups permission. Connecting to an MSK cluster.

  19. Select Next.

  20. Select the cluster's Access control methods and Encryption settings for encrypting data as it transits between clients and brokers. For more information, see Amazon MSK encryption in transit.

  21. Choose the kind of KMS key that you want to use for encrypting data at rest. For more information, see Amazon MSK encryption at rest.

  22. Select Next.

  23. Choose the Monitoring and tags you want. This determines the set of metrics you get. For more information, see Monitor an Amazon MSK Provisioned cluster. Amazon CloudWatch, Prometheus, Broker log delivery, or Cluster tags, then select Next.

  24. Review the settings for your cluster. You can go back and change settings by selecting Previous to go back to the previous console screen, or Edit to change specific cluster settings. If the settings are correct, select Create cluster.

  25. Check the cluster Status on the Cluster summary page. The status changes from Creating to Active as Amazon MSK provisions the cluster. When the status is Active, you can connect to the cluster. For more information about cluster status, see Understand MSK Provisioned cluster states.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.