Add AWS MSK IAM + TLS authentication support#850
Merged
bai merged 1 commit intolinkedin:masterfrom Aug 14, 2025
Merged
Conversation
In order to implement the IAM auth mechanism for Burrow, the following changes were required. * The iamTokenProvider struct has been implemented to hold the iam parameters provided in the toml configuration file. * A helper function which leverages the aws-msk-iam-sasl-signer-go/signer methods in order to generate the auth token has been provided. * The token is being assigned to the saramaConfig.Net.SASL structure. Document TLS+IAM configuration * tls-iam.md contains a description of the IAM implementation and configuration. * Added a commented section to config/burrow.toml which provides a IAM configuration example.
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch lets Burrow talk to Amazon MSK clusters that enforce IAM
(SASL/OAUTHBEARER) over TLS, without sidecars or external proxies.
Highlights
New config sections
[iam.*]— region, optional role-arn / profileiam = "<name>"key in[client-profile.*]to activate IAM authHelpers
iam.go– wrapsaws-msk-iam-sasl-signer-go v1.0.4and implementssarama.AccessTokenProvidersarama.go– extendsGetSaramaConfigFromClientProfileto:• validate
iam.*block• auto-enable
SASLTypeOAuth• inject the token provider
• enforce TLS when IAM is present
New dependency
github.com/aws/aws-msk-iam-sasl-signer-go→ v1.0.4Unit tests
iam.go; signer calls are stubbed.Docs
docs/msk-iam.md– overview, IAM policy snippets, EKS Pod-Identity notesexamples/burrow.toml– ready-to-run config with TLS + IAM listener (9098)Compatibility
iam.*is used without TLS or region.