Legacy implementation of dynamodb fails for named missing tables

If a table is referenced by name in the old implementation, and it doesn't exist, the run fails. 
This isn't ideal because a table deletion can break a large config and prevent updates. We don't apply this to other service types so should be able to gracefully handle this scenario.