AWS Managed Streaming for Kafka
Browse all Amazonaws APIs62
AI ReadinessAI-Aware (B-)62/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputehmac36 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision and manage Apache Kafka clusters, configurations, and SCRAM secrets on AWS without operating the underlying broker fleet.
Use for: I need to provision a new Kafka cluster, Get the bootstrap brokers for an MSK cluster, List all MSK clusters in a region, Update the broker configuration of a cluster
Not supported: Does not handle topic-level produce or consume traffic, schema registry operations, or Kafka Connect deployments - use for MSK cluster lifecycle and configuration management only.
Jentic publishes the only available OpenAPI specification for Amazon Managed Streaming for Apache Kafka (MSK), keeping it validated and agent-ready. The MSK control plane API has 36 endpoints for provisioning Kafka clusters, managing broker counts, applying broker configurations, attaching SCRAM secrets stored in Secrets Manager, and tracking cluster operations such as version upgrades and storage expansions. It does not handle topic-level produce or consume calls - those run over native Kafka protocol against the broker bootstrap endpoints. MSK is built for teams that want managed brokers, automated patching, and ZooKeeper or KRaft mode without operating the underlying instances themselves.
Install Jentic One Beta
Connect the Managed Streaming for Kafka to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Managed Streaming for Kafka, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Fkafka" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Fkafka" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Managed Streaming for Kafka API.
Provision MSK clusters via /v1/clusters and /api/v2/clusters
List and describe broker nodes for a cluster
Apply and revise Kafka broker configurations
Attach SCRAM secrets stored in AWS Secrets Manager to enable SASL/SCRAM authentication
Track long-running cluster operations such as version upgrades
Expand broker storage and update broker counts on existing clusters
Tag clusters and configurations for cost allocation
Use Cases
Patterns agents use Managed Streaming for Kafka API for, with concrete tasks.
★ Provisioning Kafka for Data Pipelines
Stand up a managed Kafka cluster for streaming ingestion pipelines that fan out events to data warehouses, search indexes, and downstream services. The MSK API provisions broker nodes across multiple Availability Zones, applies a server property configuration, and exposes bootstrap endpoints once the cluster is active. Operators avoid running ZooKeeper or KRaft directly while keeping wire-protocol compatibility with existing Kafka clients.
Create an MSK cluster named 'events-prod' with 3 broker nodes of kafka.m5.large in subnets subnet-a, subnet-b, subnet-c
SASL/SCRAM Authentication Setup
Wire SCRAM authentication into an MSK cluster by associating secrets stored in AWS Secrets Manager. The /v1/clusters/{clusterArn}/scram-secrets endpoint attaches a list of secret ARNs to the cluster, after which clients connect over SASL_SSL using the username and password recorded in each secret. This avoids embedding broker credentials in client code and works with audit logs in CloudTrail.
Attach secret arn:aws:secretsmanager:us-east-1:123:secret:msk-app-1 to cluster arn:aws:kafka:us-east-1:123:cluster/events-prod
Cluster Lifecycle Operations
Manage long-running operations such as broker count increases, storage expansions, and Kafka version upgrades through the cluster operations endpoints. The /v1/operations/{clusterOperationArn} endpoint reports operation state, target configuration, and any errors so platform teams can monitor changes without watching the AWS console. Tagging clusters and configurations supports per-team cost allocation and inventory views.
Get the status of cluster operation arn:aws:kafka:us-east-1:123:cluster-operation/abc and return the operation type and current state
AI Agent Streaming Infrastructure Operations
AI agents call the MSK API through Jentic to provision new clusters for ad-hoc workloads, fetch bootstrap brokers when wiring downstream services, and audit configuration drift across environments. Through Jentic, the agent searches by intent, loads the input schema, and executes with credentials held in the vault. This is faster than implementing SigV4 signing inside the agent runtime and prevents AWS keys from entering the LLM context.
Search Jentic for 'get kafka bootstrap brokers', load the GetBootstrapBrokers schema, and execute against cluster arn:aws:kafka:us-east-1:123:cluster/events-prod
Key Endpoints
36 endpoints — jentic publishes the only available openapi specification for amazon managed streaming for apache kafka (msk), keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/clusters
Create an MSK cluster
GET
/v1/clusters
List MSK clusters
GET
/v1/clusters/{clusterArn}
Describe a cluster
POST
/v1/configurations
Create a Kafka configuration
POST
/v1/clusters/{clusterArn}/scram-secrets
Attach SCRAM secrets to a cluster
GET
/v1/operations/{clusterOperationArn}
Describe a cluster operation
POST
/v1/clusters
Create an MSK cluster
GET
/v1/clusters
List MSK clusters
GET
/v1/clusters/{clusterArn}
Describe a cluster
POST
/v1/configurations
Create a Kafka configuration
POST
/v1/clusters/{clusterArn}/scram-secrets
Attach SCRAM secrets to a cluster
GET
/v1/operations/{clusterOperationArn}
Describe a cluster operation
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Managed Streaming for Kafka
- AI-Aware (B-)62/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility39
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
39
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
56%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Amazon MSK API by hand means building AWS Signature Version 4 signing, selecting the right regional host from kafka.{region}.amazonaws.com, polling long-running cluster operations, and handling AWS throttling and retries yourself. Through Jentic you install once, import Managed Streaming for Kafka from the API Directory, store the AWS access key and secret once, and your agent calls it.
Permission scoping
MSK puts the cluster ARN in the URL path (/v1/clusters/{clusterArn}/...), so a rule can pin your agent to one cluster: it can describe that cluster and read its bootstrap brokers and nothing else. You choose the operations it may call, so destructive ones like DeleteCluster or updating the broker configuration are not included unless you add them.
Credential isolation
Your AWS access key and secret for the MSK control plane are stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'provision an apache kafka cluster' or 'get the bootstrap brokers', and Jentic returns the matching MSK operation with its input schema so the agent calls the right endpoint without reading the AWS reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Managed Streaming for Kafka API through Jentic.
Why is there no official OpenAPI spec for Amazon MSK?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Managed Streaming for Kafka via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Amazon MSK API use?
The MSK control plane API uses AWS Signature Version 4 (SigV4) HMAC request signing. The Kafka data plane (produce and consume) uses native Kafka protocol with IAM, mTLS, or SASL/SCRAM. Through Jentic, AWS credentials sit in the encrypted vault and SigV4 signing happens at execution time.
Can I publish messages to a Kafka topic with the MSK API?
No. The MSK control plane API does not expose produce or consume operations. Use a native Kafka client connected to the bootstrap brokers returned by GetBootstrapBrokers. The MSK API handles cluster, configuration, and credential management only.
How do I provision a new Kafka cluster through Jentic?
Search Jentic for 'create kafka cluster', load the schema for POST /v1/clusters or /api/v2/clusters, submit the broker count, instance type, and subnet list, then poll GET /v1/operations/{clusterOperationArn} until the cluster is ACTIVE. Jentic handles SigV4 signing throughout.
What are the rate limits for the Amazon MSK API?
Per-region quotas apply, including a default limit on clusters per account, brokers per cluster, and configurations per region. Control plane TPS limits also apply per operation. Check the MSK service quotas in the AWS console for the values in your account.
Can I attach SCRAM secrets to an existing MSK cluster?
Yes. POST /v1/clusters/{clusterArn}/scram-secrets accepts a list of Secrets Manager secret ARNs. Each secret must be encrypted with a customer-managed KMS key and contain a JSON object with username and password fields for SCRAM authentication.
Can I monitor a cluster upgrade with the MSK API?
Yes. Long-running operations such as version upgrades and storage expansions return a clusterOperationArn that can be polled with GET /v1/operations/{clusterOperationArn}. The response includes operation type, current state, and any error details.
Can I limit what my agent is allowed to do with the Amazon MSK API?
Yes. Jentic One runs self-hosted, so your own rules decide which MSK operations and AWS credentials the agent may use. Because MSK puts the cluster ARN in the URL path (/v1/clusters/{clusterArn}/...), you can pin the agent to a single cluster and allow only read operations such as describing that cluster and fetching its bootstrap brokers. Destructive calls like DeleteCluster or updating the broker configuration stay unavailable unless you explicitly add them.
GET STARTED