Amazon MSK quota

Your AWS account has default quotas for Amazon MSK. Unless otherwise stated, each per-account quota is Region-specific within your AWS account.

Requesting a quota increase in Amazon MSK

You can request a quota increase for each Region using the Service Quotas console, AWS CLI, or a support case. If an adjustable quota isn't available in the Service Quotas console, use the AWS Support Center Console to create a service quota increase case.

Support could approve, deny, or partially approve your quota increase requests. Increases aren't granted immediately, and can take a few days to take effect.

To request an increase using the Service Quotas console

1. Open the Service Quotas console at https://console.aws.amazon.com/servicequotas/.

2. From the navigation bar, at the top of the screen, select a Region.

3. In the left navigation pane, choose AWS services.

4. In the Find services box, type msk, and then choose Amazon Managed Streaming for Apache Kafka (MSK).

5. In Service quotas, choose the Quota name for which you want to request an increase. For example, Number of brokers per account.

6. Choose Request increase at account level.

7. For Increase quota value, enter a new quota value.

8. Choose Request.

9. (Optional) To view any pending or recently resolved requests in the console, choose Dashboard in the left navigation pane. For pending requests, choose the status of the request to open the request receipt. The initial status of a request is Pending. After the status changes to Quota requested, you'll see the case number with Support. Choose the case number to open the ticket for your request.

For more information, including how to use the AWS CLI or SDKs to request a quota increase, see Requesting a quota increase in the Service Quotas User Guide.

Amazon MSK Standard broker quota

Standard broker quota

Dimension	Quota	Notes
Brokers per account	90	To request higher quota, go to the Service Quotas console.
Brokers per cluster	30 for ZooKeeper-based clusters 60 for KRaft-based clusters	To request higher quota, go to the Service Quotas console.
Minimum storage per broker	1 GiB
Maximum storage per broker	16384 GiB
Maximum TCP connections per broker (IAM Access control)	3000	To increase this limit, you can adjust the listener.name.client_iam.max.connections or the listener.name.client_iam_public.max.connections configuration property using the Kafka AlterConfig API or the kafka-configs.sh tool. It's important to note that increasing either property to a high value can result in unavailability.
Maximum TCP connections rate per broker (IAM)	100 per second (M5 and M7g instance sizes) 4 per second (t3 instance size)	To handle retries on failed connections, you can set the reconnect.backoff.ms configuration parameter on the client side. For example, if you want a client to retry connections after 1 second, set reconnect.backoff.ms to 1000. For more information, see reconnect.backoff.ms in the Apache Kafka documentation.
Maximum TCP connections per broker (non-IAM)	N/A	MSK does not enforce connection limits for non-IAM auth. You should monitor other metrics such as CPU and memory usage to ensure you do not overload your cluster because of excessive connections.
Configurations per account	100	To request higher quota, go to the Service Quotas console. To update the configuration or the Apache Kafka version of an MSK cluster, first ensure the number of partitions per broker is under the limits described in Right-size your cluster: Number of partitions per Standard broker.
Configuration revisions per account	50

Amazon MSK Express broker quota

Express broker quotas

Dimension	Quota	Notes
Brokers per account	90	To request higher quota, go to the Service Quotas console.
Brokers per cluster	30	To request higher quota, go to the Service Quotas console.
Maximum storage	Unlimited
Maximum TCP connections per broker (IAM Access control)	3000
Maximum TCP connections rate per broker (IAM)	100 per second	To handle retries on failed connections, you can set the reconnect.backoff.ms configuration parameter on the client side. For example, if you want a client to retry connections after 1 second, set reconnect.backoff.ms to 1000. For more information, see reconnect.backoff.ms in the Apache Kafka documentation.
Maximum TCP connections per broker (non-IAM)	N/A	MSK does not enforce connection limits for non-IAM auth. You should however monitor other metrics such as CPU and memory usage to ensure you do not overload your cluster because of excessive connections.
Configurations per account	100	To request higher quota, go to the Service Quotas console. To update the configuration or the Apache Kafka version of an MSK cluster, first ensure the number of partitions per broker is under the limits described in Right-size your cluster: Number of partitions per Express broker.
Configuration revisions per account	50
Max Ingress per broker	Recommended: 15.6 - 500.0 MBps	Based on instance size.
Max Egress per broker	Recommended: 31.2 - 1000.0 MBps	Based on instance size.

Express broker throughput throttle limits by broker size

The following table lists the recommended and maximum throughput throttle limit related to ingress and egress for different broker sizes. In this table, the recommended throughput is represented as Sustained performance, which is the threshold up to which your applications won't experience any performance degradation. If you operate beyond these limits on either dimension, you might get more throughput, but you might also experience performance degradation. Maximum quota is the threshold at which your cluster will throttle read/write traffic. Your applications won't be able to operate beyond this threshold.

Instance size	Sustained performance (MBps) for ingress	Maximum quota (MBps) for ingress	Sustained performance (MBps) for egress	Maximum quota (MBps) for egress
express.m7g.large	15.6	23.4	31.2	58.5
express.m7g.xlarge	31.2	46.8	62.5	117
express.m7g.2xlarge	62.5	93.7	125	234.2
express.m7g.4xlarge	124.9	187.5	249.8	468.7
express.m7g.8xlarge	250	375	500	937.5
express.m7g.12xlarge	375	562.5	750	1406.2
express.m7g.16xlarge	500	750	1000	1875

MSK Replicator quotas

• A maximum of 15 MSK Replicators per account.

• MSK Replicator only replicates up to 750 topics in sorted order. If you need to replicate more topics, we recommend that you create a separate Replicator. Go to the Service Quotas console, if you need support for more than 750 topics per Replicator. You can monitor the number of topics being replicated using the "TopicCount" metric.

• A maximum ingress throughput of 1GB per second per MSK Replicator. Request a higher quota by going through the Service Quotas console.

• MSK Replicator Record Size - A maximum of 10MB record size (message.max.bytes). Request a higher quota by going through the Service Quotas console.

MSK Serverless quota

Note

If you experience any issue with service quota limits, create a support case with your use case and requested limit.

Limits are per cluster, unless otherwise stated.

Dimension	Quota	Quota violation result
Maximum ingress throughput	200 MBps	Slowdown with throttle duration in response
Maximum egress throughput	400 MBps	Slowdown with throttle duration in response
Maximum retention duration	Unlimited	N/A
Maximum number of client connections	3000	Connection close
Maximum connection attempts	100 per second	Connection close
Maximum message size	8 MB	Request fails with ErrorCode: INVALID_REQUEST
Maximum request rate	15,000 per second	Slowdown with throttle duration in response
Maximum rate of topic management APIs requests rate	2 per second	Slowdown with throttle duration in response
Maximum fetch bytes per request	55 MB	Request fails with ErrorCode: INVALID_REQUEST
Maximum number of consumer groups	500	JoinGroup request fails
Maximum number of partitions (leaders)	2400 for non-compacted topics. 120 for compacted topics. To request a service quota adjustment, create a support case with your use case and requested limit.	Request fails with ErrorCode: INVALID_REQUEST
Maximum rate of partition creation and deletion	250 in 5 minutes	Request fails with ErrorCode: THROUGHPUT_QUOTA_EXCEEDED
Maximum ingress throughput per partition	5 MBps	Slowdown with throttle duration in response
Maximum egress throughput per partition	10 MBps	Slowdown with throttle duration in response
Maximum partition size (for compacted topics)	250 GB	Request fails with ErrorCode: THROUGHPUT_QUOTA_EXCEEDED
Maximum number of client VPCs per serverless cluster	5
Maximum number of serverless clusters per account	10. To request a service quota adjustment, create a support case with your use case and requested limit.

MSK Connect quota

• Up to 100 custom plugins.

• Up to 100 worker configurations.

• Up to 60 connect workers. If a connector is set up to have auto scaled capacity, then the maximum number of workers that the connector is set up to have is the number MSK Connect uses to calculate the quota for the account.

• Up to 10 workers per connector.

To request higher quota for MSK Connect, go to the Service Quotas console.