All Services

Analytics

Amazon Managed Streaming for Apache Kafka

Amazon Managed Streaming for Apache Kafka provides managed Apache Kafka clusters or serverless Kafka-compatible capacity while preserving Kafka APIs, topic semantics, and ecosystem integrations.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Managed Streaming for Apache Kafka.

Amazon Managed Streaming for Apache Kafka pricing and cost programs

Pricing model: Managed Kafka capacity

On-Demand
Available
Reserved Instances or reserved capacity
Available
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Broker or MCU hours · Storage · Data transfer · Connect workers

Programs and modes: Provisioned clusters · Reserved Instances · MSK Serverless · MSK Connect

Reserved pricing applies to eligible provisioned brokers; Serverless and Connect use separate dimensions.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Managed Streaming for Apache Kafka?

  • Automates broker provisioning, hardware replacement, patching, availability operations, storage options, and control-plane management for Apache Kafka workloads.
  • Maintains Kafka client and ecosystem compatibility for ordered partition logs, consumer groups, replay, stream processing, and connector integrations.
  • Supports multi-AZ clusters, IAM and other supported authentication modes, TLS, encryption, private VPC networking, monitoring, replication features, and tiered storage where available.

How to implement Amazon Managed Streaming for Apache Kafka

  1. Choose MSK Serverless for supported elastic workloads with minimal broker choices or Provisioned when broker size, storage, version, configuration, or predictable capacity needs more control.
  2. Estimate throughput, record size, retention, partition count, replication, consumer groups, replay window, and failure headroom, then create a private multi-AZ cluster with encryption and an intentional authentication mode.
  3. Create versioned topics, configure producers and consumers with multiple bootstrap brokers, durable acknowledgement and retry semantics, deploy monitoring and autoscaling where supported, and test broker loss, rebalancing, throttling, replay, and upgrades.

Amazon Managed Streaming for Apache Kafka best practices

  • For Provisioned production clusters, use three Availability Zones, replication factor of at least three, and a minimum in-sync replica value that allows one replica to be unavailable during rolling operations.
  • Keep partition counts and broker CPU or storage within current AWS guidance, preserve failure headroom, distribute leaders and traffic, control retention, and load-test whether scaling up or out actually meets latency and throughput goals.
  • Use current Kafka clients with brokers from every Availability Zone, configure idempotent production and safe acknowledgements where required, monitor consumer lag and under-replicated partitions, and make consumers tolerant of rebalances and duplicates.

Amazon Managed Streaming for Apache Kafka use cases and server impact

  • Kafka-compatible event streaming and replay
  • Change-data-capture backbones
  • Real-time application and analytics pipelines

Replaces Kafka broker and control-plane hosts plus much patching and replacement work, while topic design, client semantics, partitions, retention, schema governance, and consumer health remain owned by the team.

Official implementation resources

Commonly paired AWS services