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 unable to locate property for key attribute
- DynamoDB Is Unsupported It Cannot Be Instantiated
- AWS Lambda DynamoDB Stream Error
- boto3 dynamodb unable to locate credentials
- DynamoDB FilterExpression Not Working
- dynamodb cannot create preexisting table
- KMS Key Access Denied Error DynamoDB
- CORS Error DynamoDB
- failed to list tables not authorized dynamodb
- could not transform a dynamodb amazonserviceexception to a compatible kinesis exception
- DynamoDB Scan Not Working
- DynamoDB Not Supported Requires @DynamoDBTyped Or @DynamoDBTypeConverted
- dynamodb autoscaling not fast enough
- AWS DynamoDB Provisioning Error
- Boto3 DynamoDB KeyError
Tired of switching accounts and regions? Use Dynobase.
First 7 days are on us. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase