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 scan missing values
- dynamodb does not accept empty set
- DynamoDB Scan Not Working
- Error ValidationException: One or more parameter values were invalid: Type mismatch for key X expected: S actual: M
- AWS Lambda DynamoDB Stream Error
- AWS CLI DynamoDB Error Parsing Parameter
- sls dynamodb install not working
- dynamodb-admin command not found
- DynamoDB Local Cannot Create Preexisting Table
- an expression attribute name used in the document path is not defined
- DynamoDB Delete Not Working
- dynamodb cannot read property 's' of undefined
- boto3 dynamodb unable to locate credentials
- DynamoDB failedbatch retry
- dynamodb converter not found for enhancedtype
Tired of switching accounts and regions? Use Dynobase.
Try 7-day free trial. No credit card needed.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase