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)
- a bytes-like object is required not binary dynamodb
- DynamoDB Delete Not Working
- CORS Error DynamoDB
- DynamoDB Local Docker Not Working
- DynamoDB Is Not Null
- dynamodb docker unable to open database file
- dynamodb cannot convert undefined to object
- DynamoDB Error All Attributes Must Be Indexed
- name key is not defined dynamodb
- DynamoDB TTL Not Working
- DynamoDB Item Does Not Exist
- boto3 dynamodb unable to locate credentials
- DynamoDB Key element does not match the schema
- dynamodb query key condition not supported
- DynamoDB Local Cannot Create Preexisting Table
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase