In version 1.X.X, we have added migration support for DynamoDB's pay-per-request (AKA on-demand) billing. Thus, we no longer provide default provisioned throughput of [1,1] when creating tables and indexes via migrations. If any of your table/index creation files do not explicitly specify values for provisioned_throughput, you'll want to update those.
To create a pay-per-request table, you would add the billing_mode: :pay_per_request option to that table; you should not provide provisioned_throughput for pay-per-request tables, nor their indexes.
In version 1.1.0, we introduced a new configuration option, the boolean :dynamodb_local. Due to slight differences in behaviour between production and local versions of DynamoDB, there are some times when special handling needs to be applied.
This configuration option defaults to false, so it assumes that you are running against production DynamoDB unless you explicitly set it to true. Although you would probably be fine if you didn't set this, we highly recommend setting it in any environment that you will be running against the local development version of DynamoDB.
In order to make sure your local version of DynamoDB is up to date with the current production features, please use the latest release of DynamoDB local. As of spring 2019, the latest version is 1.11.477, released on February 6, 2019.