feat: support for credentials in AWS Secrets Manager #174
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.
Add support for credentials stored in AWS Secrets Manager.
The Amazon Resource Name (ARN) of a secret in AWS Secrets Manager can be provided
in a cluster.yaml file as a way to provide credentials for SASL authentication. The secret in Secrets Manager must have a value in the format
shown below, identical to what AWS MSK requires.
An example of secrets manager being used can be seen below. Be sure to include the 6Random-Characters
AWS Secrets Manager tacks on to the end of a secrets ARN.
Further documentation on how can be used can be seen in
examples/auth/cluster.yaml
or the README