You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm integrating your tool into my AWS Kafka infrastructure, and so far it looks like a great fit, but I've stumbled upon a (seemingly) missing feature that I think could be useful.
We have a bunch of Kafka clusters in different regions, so instead of creating separate local AWS profiles for them we use a unified profile with explicit --assume-role for each of the regions/accounts. I can't make it work with topicctl though: AWS_ROLE_ARN is not documented in the AWS Go SDK and doesn't seem to do anything. The only way I could find was generating a bunch of profiles for each of the roles, which quickly gets out of hands.
There appears to be a way to assume a role programmatically in the SDK, so I'm wondering if you could offer an extra configuration option for mechanism: AWS-MSK-IAM, such as assume-role? It'd help a lot.
The text was updated successfully, but these errors were encountered:
Ok, I have a draft of a fix in #67. Can you give it a try and let me know whether it works for you? Unfortunately, I don't have access to an MSK cluster at the moment to test it on. Thanks.
I'm integrating your tool into my AWS Kafka infrastructure, and so far it looks like a great fit, but I've stumbled upon a (seemingly) missing feature that I think could be useful.
We have a bunch of Kafka clusters in different regions, so instead of creating separate local AWS profiles for them we use a unified profile with explicit
--assume-role
for each of the regions/accounts. I can't make it work withtopicctl
though: AWS_ROLE_ARN is not documented in the AWS Go SDK and doesn't seem to do anything. The only way I could find was generating a bunch of profiles for each of the roles, which quickly gets out of hands.There appears to be a way to assume a role programmatically in the SDK, so I'm wondering if you could offer an extra configuration option for
mechanism: AWS-MSK-IAM
, such asassume-role
? It'd help a lot.The text was updated successfully, but these errors were encountered: