Brain fart on my part, too much time working on Play apps. Should have been a FuturePool and not a regular Future. I took a look at their Async client initially but it is based on Java futures which are pretty gross and hard to work with in Scala. The Injection from java future to twitter future that behaves as expected could get a little messy. 

My personal preference would be to continue to use the blocking dynamo client and just dispatch the blocking operations to a FuturePool which will give us a non-blocking Store that plays nicely with Scala and Twitter Futures.