Add offline IAM access key review helper#78
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 ignored due to path filters (1)
📒 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 |
/claim #55
Scope
This is a separate Phase 6/9 offline IAM access-key review slice. It does not overlap with the existing Civil ID, S3 env, SQS, MediaConvert, SES/mailers, Xero, Cloudinary, secret-scanning, bucket-guardrail, service-token, CloudTrail, Slack, or recovery-audit PRs.
No live AWS/IAM calls, key rotation/deletion, bucket policy changes, candidate data, access keys, secret keys, account IDs, private exports, or raw CloudTrail records were accessed or included.
Summary
tools/audit-iam-access-keys.mjs, an offline CLI for maintainer-exported IAM access-key inventoriesValidation
node tools/check-iam-access-key-review.mjsnode --check tools/audit-iam-access-keys.mjsnode --check tools/check-iam-access-key-review.mjsgit diff --check HEAD~1 HEADThe regression check verifies that both Markdown and CSV reports include the expected remediation actions without leaking the synthetic full key IDs from the fixture.