Open th3cod3r opened 7 months ago
Same issue against an AWS MSK setup. Network access is set up, and getting the same error even with assuming a role that has full access to the AWS account. The error message is not very useful unfortunately
I had the same issue. This has more or less been addressed in the readme. In my case, I had to instantiate the provider as so:
data "aws_msk_cluster" "main" {
cluster_name = "MyClusterName"
}
data "aws_arn" "msk_cluster" {
arn = data.aws_msk_cluster.main.arn
}
provider "kafka" {
bootstrap_servers = split(",", data.aws_msk_cluster.main.bootstrap_brokers_sasl_iam)
tls_enabled = true
sasl_mechanism = "aws-iam"
sasl_aws_region = data.aws_arn.msk_cluster.region
}
I then assumed the required AWS role before running terraform apply
.
Hey @Mongey,
I was getting error with my tf file that Error: kafka: client has run out of available brokers to talk to: EOF
Here is tf file
Requirement:
The kafka is a shared kafka and I just only want to connect in it with a specific tenant id as i have to separate the kafka database with the tenant id (When a another server will connect then i have some producer that will auto-insert into it with the particular tenant id which i defined). And have to apply some acl for security as well.