1 Answer
- Newest
- Most votes
- Most comments
0
There is an extra comma after security groups that was causing the issue. It's resolved now.
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- How do I troubleshoot common issues when using my Amazon MSK cluster with SASL/SCRAM authentication?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
Hi, Please share your code with us.
@iwasa
import { KafkaClient, CreateClusterV2Command,ListClustersV2Command } from "@aws-sdk/client-kafka";
let config = { maxAttempts: 1, region: "region", credentials:{ accessKeyId: "xx-xxx-xxxx", secretAccessKey: "xxx-xxx-xxx" } }
const client = new KafkaClient(config);
const params = { ClusterName: 'mks-cluster', Serverless: { VpcConfigs: [ { SubnetIds: [ 'xxx', 'yyy', 'zzz' ], SecurityGroupIds: [ 'abc', ] }, ], ClientAuthentication: { Sasl: { Iam: { Enabled: true } } } }, Tags: { 'msk-tag': 'value', } };
const command = new CreateClusterV2Command(params);
try{ const response = await client.send(command); // after this I get response as - "creating" and later on it fails