Error: dynamodb does not support null values
Answered by Rafal Wilinski
What's Causing This Error
Earlier, DynamoDB did not allow you to store empty strings or null values in an item. If you do so, DynamoDB will throw an error indicating that it does not support null values.
Solution: Here's How To Resolve It
However, as of 18th May 2020, DynamoDB no longer runs into this error and has introduced support for null values. Although, keep in mind that you may still run into this error if you are trying to store a null value on an attribute that acts as the partition key for the table or GSI.
Other Common DynamoDB Errors (with Solutions)
- dynamodb put function not working
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- dynamodb list_append returns true but does not work
- DynamoDB failedbatch retry
- dynamodb cannot pickle '\_thread.lock' object
- DynamoDB Failed To Compute Node presentation
- Unable to start DynamoDB Local process
- KMS Key Access Denied Error DynamoDB
- dynamodb net scan condition or not working
- an expression attribute name used in the document path is not defined
- dynamodb streams missing events
- a socket operation was attempted to an unreachable network dynamodb
- dynamodb cannot read properties of undefined (reading 'bytelength')
- aws.dynamodb.converter.unmarshall not working
- dynamodb getItem() is not a function
Tired of switching accounts and regions? Use Dynobase.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase