Add n8n S3 workflow audit helper#85
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 |
/claim #55
Summary
n8n-s3-accessinvestigation path.Scope
This is a separate Phase 6 helper slice. It does not overlap with the Civil ID backend/frontend PRs, S3 env-var credential PRs, IAM credential CSV review, CloudTrail event export audit, S3 bucket posture audit, bucket guardrails, or AWS Support evidence-package helpers.
No live AWS/IAM/S3/n8n calls are made. No key rotation, deletion, bucket policy change, workflow mutation, candidate data access, or real credential export is included.
Verification
node tools/check-n8n-s3-workflow-audit.mjsnode tools/audit-n8n-s3-workflows.mjs --workflows tools/fixtures/n8n-s3-workflows.sample.json --format markdownnode tools/audit-n8n-s3-workflows.mjs --workflows tools/fixtures/n8n-s3-workflows.sample.json --format csvgit diff --checkThe fixture uses synthetic placeholder values and avoids real AWS-key-shaped sample credentials.