aws-sam-cli
CLI tool to build, test, debug, and deploy Serverless applications using AWS SAM
Runssource: GitHubhomepagePythonApache-2.0commit 3a8d3c2d0b7e
Python, Apache-2.0 licensed. The project labels itself: api gateway, aws, docker, lambda, python, sam, serverless and serverlessapplicationmodel.
aws-sam-cli runs. An Argusic agent installed it in 11 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
SAM CLI v1.166.2 builds, all 9435 unit tests pass at 94% coverage, and the CLI validates SAM templates successfully
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test_updates_imageuri_when_pointing_to_local_archive wrote to path escaping /work/repo (PermissionError)2 minutes
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- samdev --version returned 'SAM CLI, version 1.166.2'; samdev validate -t /tmp/test-template.yaml --region us-east-1 exited 0 returning 'is a valid SAM Template'; pytest tests/unit reported 9435 passed, 25 skipped, 94% coverage
- Model tokens used
- 37,771
- Exact commit tested
- 3a8d3c2d0b7e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All done. Here's the final report: **Install**: `pip install -e '.[dev]'` succeeded. Python 3.12.3, pip 26.2.1. **Error found & fixed**: One test (`test_updates_imageuri_when_pointing_to_local_archive`) tried to… **Tests**: 9435 passed, 25 skipped, 31 subtests passed, 94% coverage — clean run. **CLI verified**: `samdev --version` printed `SAM CLI, version 1.166.2`. `samdev validate -t /tmp/t… tokens used 37,771 All done. Here's the final report: **Install**: `pip install -e '.[dev]'` succeeded. Python 3.12.3, pip 26.2.1. **Error found & fixed**: One test (`test_updates_imageuri_when_pointing_to_local_archive`) tried to… **Tests**: 9435 passed, 25 skipped, 31 subtests passed, 94% coverage — clean run. **CLI verified**: `samdev --version` printed `SAM CLI, version 1.166.2`. `samdev validate -t /tmp/t…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 11 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
api-gatewayawsdockerlambdapythonsamserverlessserverlessapplicationmodel
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aws-sam-cli)Questions
- Does aws-sam-cli run?
- Yes. aws-sam-cli runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test aws-sam-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3a8d3c2d0b7e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test aws-sam-cli?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does aws-sam-cli take to install?
- 11 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does aws-sam-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing aws-sam-cli?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for aws-sam-cli?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.