[TT-14473] - support for encrypted aws kinesis #876

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.

Sign up for GitHub

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

Closed

LLe27 wants to merge 12 commits into master from tt-14473-support-for-encrypted-aws-kinesis

Closed

[TT-14473] - support for encrypted aws kinesis #876

fix security issues

probelabs / Visor: security succeeded Oct 9, 2025 in 4m 59s

✅ Check Passed (Warnings Found)

security check passed. Found 1 warning, but fail_if condition was not met.

Details

📊 Summary

Total Issues: 1
Warning Issues: 1

🐛 Issues by Category

📚 Documentation (1)

⚠️ README.md:1363 - The documentation for the new kms_key_id feature does not mention the required AWS IAM permissions (kinesis:DescribeStream and kinesis:StartStreamEncryption). This omission can lead to deployment failures and may cause users to grant overly broad permissions to resolve the issue, violating the principle of least privilege.

Generated by Visor - AI-powered code review

Annotations

Check warning on line 1363 in README.md

probelabs / Visor: security

documentation Issue

The documentation for the new `kms_key_id` feature does not mention the required AWS IAM permissions (`kinesis:DescribeStream` and `kinesis:StartStreamEncryption`). This omission can lead to deployment failures and may cause users to grant overly broad permissions to resolve the issue, violating the principle of least privilege.

Raw output


            Update the `README.md` to explicitly state the required IAM permissions. This ensures users can configure their infrastructure securely and correctly from the start.

View more details on probelabs