MSK Serverless (Apache Kafka)
An MSK Serverless Apache Kafka cluster with no brokers to size - SASL/IAM authentication only, encryption in transit and at rest always on, multi-AZ placement, and a locked-down security group.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o aws-msk-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-msk/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-msk-1.0.0.sigstore.json \
aws-msk-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "d817a5cb490611f5cf92265638fa4b327ffeb51eba2314d06c5fb6b881462341 aws-msk-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "msk" {
source = "www.iac-bazaar.com/iac-bazaar/aws-msk/aws"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-msk?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [MSK Serverless (Apache Kafka)](https://www.iac-bazaar.com/catalog/aws-msk?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "msk" {
source = "www.iac-bazaar.com/iac-bazaar/aws-msk/aws"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
aws-msk
Amazon MSK Serverless — a fully-managed, on-demand Apache Kafka cluster with
no brokers to size, patch, or pay for at idle. You provision topics, not
instances; capacity scales automatically. Works with Terraform and OpenTofu
(>= 1.6), AWS provider >= 6.0, < 7.0. Secure by default and self-contained:
authentication is SASL/IAM only (the single mode serverless supports),
encryption in transit and at rest is always on, the cluster is never publicly
reachable, and the networking pieces (default-VPC placement + a locked-down
security group) are created for you, so a minimal cluster applies with just a
cluster_name.
Why serverless: it skips broker provisioning entirely (cheaper and faster to stand up than provisioned MSK, and nothing to right-size). It is billed per partition-hour, storage, and throughput rather than per broker-hour — there are no idle instances, but an empty cluster still carries a small hourly base while it exists, so tear down test clusters promptly.
Secure defaults:
- SASL/IAM authentication — every client authenticates and authorizes through IAM. There are no plaintext listeners and no SCRAM secrets to rotate (serverless does not offer unauthenticated or TLS-mutual-auth modes).
- Encryption in transit and at rest — always on, managed by the service;
clients speak Kafka over TLS on port
9098. - No public exposure — access is via a module-created security group that
opens the Kafka IAM port only to
allowed_cidrs/allowed_security_group_ids(no ingress at all by default). - Multi-AZ placement — the cluster spreads its network interfaces across 2–3 Availability Zones (default-VPC subnets when you don't pin your own).
Security notes
- Authorization is IAM-driven: grant the smallest set of
kafka-cluster:*actions your producers/consumers need, scoped to this cluster's ARN and the specific topic/group ARNs (built fromcluster_uuid). Avoid wildcard topic access. - Keep
allowed_cidrs/allowed_security_group_idsas tight as possible — prefer granting an application security group over a CIDR range. The default is no ingress at all. - For real deployments pin
subnet_idsto private subnets (in 2–3 AZs) instead of relying on the default-VPC fallback.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
aws-mq
deployment_mode defaults to SINGLE_INSTANCE, and Amazon MQ reboots the instance to patch it - so a single broker has planned downtime on AWS's schedule. Active/standby across two AZs, both log streams on, and passwords in a separate variable from users, because a sensitive value cannot be a for_each argument at all.
aws-kinesis-firehose
Without error_output_prefix, records Firehose could not process are written into the same prefix as the ones it could, wrapped in an error envelope that whatever reads the prefix treats as data. Nothing reports it.
aws-eventbridge
A custom EventBridge event bus, a pattern-filtered rule, and a target wired end-to-end - encryption at rest always on, least-privilege log delivery, and a 24h retry policy with optional DLQ.
aws-kinesis
A Kinesis Data Stream with KMS encryption at rest on by default and ON_DEMAND capacity (no shard math), plus optional enhanced fan-out consumers and IAM-only access.
aws-ses
An SES v2 sending stack - a configuration set with an optional domain/email identity (Easy DKIM) - with TLS required, bounce/complaint suppression, and reputation metrics to CloudWatch.
aws-sns
SNS standard/FIFO topic with encryption, delivery policies, and SQS/Lambda/email subscriptions.