- Newest
- Most votes
- Most comments
Hi JP - any data transfer that happens within the cluster (e.g., data replication between brokers) is included in the cost of the MSK brokers so you don't pay separately for it, and this cost does not vary.
For data in and out of the cluster, standard data transfer rates apply to this traffic.
If your EC2 clients are in the same AZ and region as the MSK broker it's connected to, per data transfer pricing the cost per GB is $0. If your clients are sending traffic to/from brokers in different AZs in the same region your clients generate cross AZ data transfer usage with a cost per GB that varies by the region the traffic is in. If your clients are in a different region than the MSK cluster, your clients generate cross region data transfer usage with a cost that varies by region source and region destination.
You can back into the AZ of the broker using the subnet.
Thank you. So I could do some setup to constrain communication between an EC2 instance and a broker in one AZ, but since that broker may not be a leader for a partition, I'd still need to make cross-AZ requests to get at all the data and hence incur cross-AZ charges?
JP
Correct. If your partition leader is in a different AZ than your producer/consumer, then you will incur cross-AZ charge.
Relevant content
- asked a month ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago