Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protocols used in allowed_cidr_blocks don't include SASL/SCRAM public cluster #97

Open
lplazas opened this issue Aug 1, 2023 · 0 comments
Labels
bug 🐛 An issue with the system

Comments

@lplazas
Copy link

lplazas commented Aug 1, 2023

Describe the Bug

When using the module, if you specify a list of allowed_cidr_blocks, a security group is created and a rule is added for each combination of cidr block and every one of the protocols defined here:

The list does not contain 9196, which is the port used with SASL/SCRAM when having a publicly accessible cluster. Attached is an example image.

Screenshot 2023-08-01 at 15 31 10

Expected Behavior

Access to 9196 should also be whitelisted for the cidr_blocks specified.

Steps to Reproduce

Create a cluster and then make it publicly accessible by satisfying first the requirements listed here: https://docs.aws.amazon.com/msk/latest/developerguide/public-access.html

Screenshots

No response

Environment

No response

Additional Context

No response

@lplazas lplazas added the bug 🐛 An issue with the system label Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system
Projects
None yet
Development

No branches or pull requests

1 participant