I just found a testConcurrentTableCreations DDB table lurking in a region, presumably from an interrupted test. Luckily test/resources/core-site.xml forces the r/w capacity to be 10, but it could still run up bills.
- explicitly set capacity = 1 for the test
- and add comments in the testing docs about keeping cost down.
I think we may also want to make this a scale-only test, so it's run less often