dynamoDB | Node JS module for accessing Amazon DynamoDB | Runtime Evironment library

Your problem is that you have set SESSION_CONNECTION=session, but your SESSION_DRIVER=default, so you have to use SESSION_DRIVER=database in your .env. See the config/session.php:

It looks like you're modeling the one-to-many relationship between Games and Results using a complex attribute (e.g. a list or objects) on the Game item. This is a completely valid approach to modeling one-to-many relationships and is best used when 1) the results data doesn't change (or change often) and 2) you don't have any access patterns around Results.

Since it sounds like you do have access patterns around Results, you'd be better off storing your Results in their own items.

For example, you might consider modeling results in the user partition with a PK=USER#user_id SK=RESULT#game_id. This would allow you to fetch results by User ID (QUERY where PK=USER#user_id SK begins_with RESULT). Alternatively, you could model results with a PK=RESULT#game_id SK=USER#user_id and create a GSI that swaps the PK/SK's which will allow you to group results by User.

I don't know the specifics around your access patterns, but can say that you'll need to move results into their own items if you want to support access patterns around game results.

Going with the WCU calculation guide here it looks like BatchWriteItem and PutItem both follows the same rounding off calculation for the size and will have same WCU consumed.

For PutItem, UpdateItem, and DeleteItem operations, DynamoDB rounds the item size up to the next 1 KB. For example, if you put or delete an item of 1.6 KB, DynamoDB rounds the item size up to 2 KB.

BatchWriteItem—Writes up to 25 items to one or more tables. DynamoDB processes each item in the batch as an individual PutItem or DeleteItem request (updates are not supported). So DynamoDB first rounds up the size of each item to the next 1 KB boundary, and then calculates the total size. The result is not necessarily the same as the total size of all the items. For example, if BatchWriteItem writes a 500-byte item and a 3.5 KB item, DynamoDB calculates the size as 5 KB (1 KB + 4 KB), not 4 KB (500 bytes + 3.5 KB).

After some trials and errors I figured out the solution for my own question

1- The GCM part of the payload should be a string not a json 2- The message parameter should have an attribute that explicitly sets the mime type of the payload to Json

Taking all that into consideration

At this time, AWS has no direct way to do this (though it looks like you can export to some service, then import from that service into an existing table).

I ended up writing my own code to do this.

GetItem() requires you to use the primary key.

You'll need to specify both hash(aka partition) and sort keys.

The problem is that your local machine doesn't have an instance profile.

If you're looking to consume AWS services from your local machine, you will have to use a credentials provider that retrieves the information locally. I recommend using DefaultAWSCredentialsProviderChain, which looks for local configuration (either in $HOME/.aws or via environment variables or system properties), and also supports instance profiles (in case you're running on an EC2 instance). That's why removing amazonDynamoDB.setCredentials(new InstanceProfileCredentialsProvider(false)); worked

I exited the process after the return from ExecuteAsync(). That was the problem. When I let it run I can see the data slowly build up. However, in the bulk insert I used a Task.Wait() because there was nothing to do until the records had been loaded. However, Iridium's answer above assited me with the second issue that revolved around ProvisionedThroughput exceptions.

There are a couple of problems in your code:

1. you need to parse the event body if it's JSON using Item=json.loads(event['body'])
2. you need to stringify the returned dict using 'body': json.dumps(response)