Amazon MSK pricing

With Amazon MSK, you pay only for what you use. There are no minimum fees or upfront commitments. You pay for the time your broker instances run, the storage you use monthly, and standard data transfer fees for data in and out of your cluster. You do not pay for Apache ZooKeeper nodes that Amazon MSK provisions for you, or data transfer that occurs between brokers and nodes within clusters.

You pay an hourly rate for Apache Kafka broker instance usage (billed at one-second resolution), with varying fees depending on the size of the broker instance and active brokers in your Amazon MSK clusters. See the Broker Instance Pricing Tables for details.

You also pay for the amount of storage you provision in your cluster. This is calculated by adding up the GB provisioned per hour and dividing by the total number of hours in the month, resulting in a "GB-months" value, as shown in the pricing example. See the Broker Storage Pricing Tables for details. You also have the option to provision additional storage throughput independently, charged by the amount you provision in MB/s per month. This is calculated by adding up MB/s provisioned per hour per broker and dividing by the total number of hours in the month, resulting in a “MB/s-months” value, as shown in (optional) Provisioned Storage Throughput Example.

You are not charged for data transfer between brokers or between Apache ZooKeeper nodes and brokers. You will pay standard EC2 rates for data transferred in and out of Amazon MSK clusters.

You can also enable private connectivity (powered by Amazon PrivateLink) if you need to connect your Apache Kafka clients in one or more VPCs to a MSK cluster in a different VPC. With this feature, you pay an hourly rate for each cluster and authentication scheme that has private connectivity turned on. An authentication scheme is used by customers to authenticate the client requests to the MSK cluster. Additionally, you also pay per GB of data processed through private connectivity. You will pay standard Amazon PrivateLink charges for the for the Amazon MSK Managed VPC connections used by your Apache Kafka clients to connect privately to the cluster.

You pay an hourly rate for connector usage (billed at one-second resolution), with varying fees depending on the number of workers you use for your connector and the size of each worker, measured in number of MSK Connect Units (MCUs). Each MCU provides 1 vCPU of compute and 4 GB of memory. See the pricing table for details.

If two kafka.t3.smalls are active in the China (Ningxia) region, and your brokers use 50GB of storage* for 31 days in March, you would pay the following for the month:

Broker instance charge

Instance usage (in hours) = 31 days x 24 hrs/day x 2 brokers = 1,488 hours x ¥ 0.2098 (price per hour for a kafka.t3.small) = ¥ 312.18

Storage charge

Storage usage in GB-Hours = 50 GB x 1 month = 50 GB-Months x ¥ 0.664 (the price per GB-Month in China (Ningxia) region) = ¥ 33.2

Total charge = ¥ 312.18 (broker instance charge) + ¥ 33.2 (storage charge) = ¥ 345.38, which is ¥ 11.14/day.

*This workload represents a 100KB/s ingest rate with 24 hour retention and replication factor of 2. Data transfer charges apply and are estimated to be ¥ 33.2/month for this workload.

If three kafka.m5.larges are active in the China (Ningxia) region, and your brokers use 1TB of storage for 15 days in March and 2TB of storage for the final 16 days in March, you would pay the following for the month:

Broker instance charge

Instance usage (in hours) = 31 days x 24 hrs/day x 3 brokers = 2,232 hours x ¥ 1.485 (price per hour for a kafka.m5.large) = ¥ 3314.52

Storage charge

Storage usage in GB-Hours = [1000 GB x 15 days x (24 hrs/day)] + [2000 GB x 16 days x (24 hrs/day)] = 1,128,000 GB-Hours

Convert GB-Hours to GB-Months to calculate the monthly charge:

1,128,000 GB-Hours / 24 hrs / 31 days = 1,516.13 GB-Months x ¥ 0.664 (the price per GB-Month in China (Ningxia) region) = ¥ 1006.71

Total charge = ¥ 3314.52 (broker instance charge) + ¥ 1006.71 (storage charge) = ¥ 4321.23

(optional) Provisioned Storage Throughput example
If you choose to turn on provisioned storage throughput and provision 300 MB/s of storage throughput for 31 days in your Amazon MSK cluster with 3 brokers in the China (Ningxia) Region, you would pay the following additional charge on top of the broker instance and storage charges as shown in above examples:

Total charge = (broker instance charge) + (storage charge) + (provisioned storage throughput charge)

(optional) Multi-VPC private connectivity example
If you have producers and consumers in different VPCs or Amazon Web Services accounts than your Amazon MSK cluster with 3 brokers in the China (Ningxia) region and you ingest 2MB/s of data and have 2 consumers reading all the data, you can choose to turn on multi-VPC private connectivity to enable cross-VPC connectivity. You would pay the following additional charge on top of the broker instance and storage charges as shown in above examples:

Total MSK charges = (broker instance charge) + (primary storage charge) + (multi-VPC private connectivity charges). 

Let’s assume you have three kafka.m5.large instances active in the China (Ningxia) Amazon Region. You want to retain data for a total of 30 days with 1-days data in the primary storage. You are ingesting 2MB/s of data into your cluster. You want to provision 1TB of primary storage for your real-time processing and store the last 30-days’ worth of data in the low-cost tier. You also want to read all the data stored in the low-cost tier with one application.

Total charges = (broker instance charge) + (primary storage charge) + (low-cost tier charge) + (low-cost tier retrieval charges)

If you have three express.m7g.larges active in the China (Ningxia) Region, and you ingest and store 1 TB of data for 31 days in March, you will pay the following for the month:

Total charge = (broker instance charge) + (data-in charge) + (storage charge)

Let’s say you use Amazon MSK Connect to stream data from a topic in your Amazon MSK cluster to an Amazon Simple Storage Service (S3) bucket in the China (Ningxia) Region, and your connector is configured as follows:

Autoscale two to four workers, with each worker using 1 MCU. During the work day (eight hours), the connector scales out to four workers, and after the work day is over (16 hours), it scales down to two workers.

In this case, you would pay the following for the month:

Total charge = Apache Kafka Connect worker charge