dynamodump

Simple backup and restore for Amazon DynamoDB using AWS SDK for Python (boto3)

Runs with mockssource: GitHubPythonMITcommit 58754125a134

Python, MIT licensed. The project labels itself: aws, backup, dynamodb, hacktoberfest, python, python3 and restore.

dynamodump runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

dynamodump installs from source in a Python venv, the dynamodump CLI responds to --help, the backup/restore workflow works against a moto-mocked DynamoDB endpoint, and the bundled unit tests (test_data, test_schema) both pass after adjusting TableSizeBytes to match moto's zero return value.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
876
forks
282
open issues
4
watchers
19
size
0 MB
created
last push

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.

Time lost to each failure while testing dynamodump, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • moto 5.x moto_server rejects region 'local' (not a real AWS region)3 minutes
  • PEP 668 externally-managed-environment blocks system-wide pip install1 minute
  • moto always returns TableSizeBytes=0; test fixture had 28 causing test_schema assertion failure1 minute
Install time
7 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
Completed restore + backup workflow against moto mock (both in-process and standalone server), then ran bundled unit tests: tests.test.TestDynamoDump.test_data ok, test_schema ok, 2 tests passed
Model tokens used
188,220
Exact commit tested
58754125a134
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

2. **Standalone server** (`moto_server` on port 8000 with `--host` mode): same workflow via actual …
tokens used
188,220
Here's the complete report:
**Installation**: Created Python venv, installed dynamodump from source (editable) with pip. Depend…
**Errors encountered**:
- Debian PEP 668 guard blocked system-wide pip. Fix: used venv.
- moto 5.x `moto_server` rejects region `"local"` (it's not a real AWS region). Fix: used `us-east-…
- moto reports `TableSizeBytes=0` unconditionally; the fixture had `28`. Fix: updated fixture to `0…
**Verification**: Ran the full restore→backup→verify cycle through two paths:
1. **In-process** (`mock_aws` context manager): restore testTable→testRestoredTable, backup testRes…
2. **Standalone server** (`moto_server` on port 8000 with `--host` mode): same workflow via actual …

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

  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 7 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 aws projects Argusic has installed and timed, dynamodump was the 7th fastest to reach a running state, and 10 of 12 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.04
Argusic Runner1/3Runs with mocks92.000.14

Topics (from GitHub)

awsbackupdynamodbhacktoberfestpythonpython3restore

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/dynamodump.svg)](https://argusic.com/subject/dynamodump)

Questions

Does dynamodump run?
dynamodump runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test dynamodump?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 58754125a134. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test dynamodump?
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 dynamodump take to install?
7 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 dynamodump need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing dynamodump?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does dynamodump compare with the alternatives?
Of the 12 aws projects Argusic has installed and timed, dynamodump was the 7th fastest to reach a running state, and 10 of 12 reached one at all.
Where is the evidence for dynamodump?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion