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 converter not found for enhancedtype
- dynamodb mapper save not persisting
- DynamoDB sorting is not supported for scan expressions
- AWS CLI DynamoDB Error Parsing Parameter
- KMS Key Access Denied Error DynamoDB
- DynamoDB GetItem no item
- dynamodb cannot convert undefined to object
- DynamoDB Failed To Compute Node presentation
- DynamoDB could not invoke null on class
- DynamoDB string set cannot be empty
- DynamoDB FilterExpression Not Working
- DynamoDB scan filter not working
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- DynamoDB console unable to delete this item
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase