Skip to content

Add offline IAM access key review helper#78

Open
lpg-it wants to merge 1 commit into
BAWES-Universe:masterfrom
lpg-it:fix/iam-access-key-review
Open

Add offline IAM access key review helper#78
lpg-it wants to merge 1 commit into
BAWES-Universe:masterfrom
lpg-it:fix/iam-access-key-review

Conversation

@lpg-it
Copy link
Copy Markdown

@lpg-it lpg-it commented May 15, 2026

/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

  • add tools/audit-iam-access-keys.mjs, an offline CLI for maintainer-exported IAM access-key inventories
  • match exposed suffixes such as DOBNJ/55KF/OFLT/XW5I/TMEZ while redacting full key IDs to suffix-only output
  • report active exposed keys, inactive keys ready for evidence-backed deletion, stale active keys, unused active keys, and missing owner/service/environment metadata
  • emit Markdown or CSV action plans for monthly IAM review and AWS Support evidence preparation
  • add a synthetic fixture, a local regression check, and a runbook linked from the README

Validation

  • node tools/check-iam-access-key-review.mjs
  • node --check tools/audit-iam-access-keys.mjs
  • node --check tools/check-iam-access-key-review.mjs
  • git diff --check HEAD~1 HEAD

The regression check verifies that both Markdown and CSV reports include the expected remediation actions without leaking the synthetic full key IDs from the fixture.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 15, 2026

Warning

Rate limit exceeded

@lpg-it has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 24 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 67f3df47-a39e-44b0-9165-f8fe7dc0cd43

📥 Commits

Reviewing files that changed from the base of the PR and between 7b023ff and c9717fb.

⛔ Files ignored due to path filters (1)
  • tools/fixtures/iam-access-keys.sample.csv is excluded by !**/*.csv
📒 Files selected for processing (4)
  • README.md
  • docs/security/iam-access-key-review.md
  • tools/audit-iam-access-keys.mjs
  • tools/check-iam-access-key-review.mjs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant