OSCER-457: use explicit key policies#1032
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Probably requires actual architecture changes |
Ticket
Part of OSCER-457
Changes
Explicit iam policy documents added to kms keys in:
Context for reviewers
Upgraded checkov tests require explicit iam policies for kms keys. Added the default kms iam policy (copied from infra/modules/storage/encryption) to all our kms keys.
Unsure if it is possible to DRY this up...
Testing
Testing done in the oscer pr.