Why it failed
The AWS error code and message, with a likely cause for common local failures.
Lenslet AWS access review for CI
Run your tests against a local AWS emulator. Lenslet records every call, explains failures, and flags new IAM permissions in the pull request.
The macOS app is not notarized: the first time, use Open Anyway in System Settings → Privacy & Security.
Every call, with the AWS error in its row and the request and response a click away.
The AWS error code and message, with a likely cause for common local failures.
Each call becomes an IAM action on a resource, implied permissions included.
lenslet.lock lists your project’s access, one permission per line, sorted.
One comment per pull request; CI fails until someone accepts new access.
--check --strict also fails on lock lines the run did not use.
lenslet policy writes an IAM policy, leaving out lines only tests need.
Start your emulator first: AWS Emulator, moto and LocalStack all work. lenslet init writes the lock and a CI workflow; commit both.
Install (Linux, macOS)
curl -fsSL https://github.com/hxddh/lenslet/releases/latest/download/install.sh | sh First run: the lock and the CI workflow
lenslet init -- npm test Fail when the code needs access the lock lacks
lenslet run --check -- npm test ~/.lenslet/runs keep raw headers and bodies, readable only by you; the last 20 are kept. No. It is the access your tests exercised, mapped by rules. Code paths the tests never reach are not in the lock.
Resources are read for S3, DynamoDB, SQS, SNS, Lambda, Secrets Manager, KMS, STS, IAM, EventBridge and Step Functions. Other services get * .
No. There are builds for macOS (universal) and Linux (x86_64 and aarch64), including a static CLI for Alpine and CI images.