Error: dynamodb converter not found for enhancedtype

Answered by Rafal Wilinski
Last updated: October 23rd, 2026
Solution
Converter not found for EnhancedType means the Java 2.x Enhanced Client has no conversion rule for a mapped property's Java type. The missing rule may be for a custom class, a collection element or a normal type whose default provider was replaced.
- Read the full EnhancedType in the exception, including generic parameters. Avoid raw collection types that hide element information.
- For a custom scalar representation, implement AttributeConverter and annotate the getter with @DynamoDbConvertedBy.
- For a nested document object, provide a compatible bean or static table schema instead of pretending it is a scalar.
- If configuring converterProviders, include DefaultAttributeConverterProvider when ordinary built-in conversions are still needed. An explicit provider list replaces the default chain.
@DynamoDbBean(converterProviders = {
CustomConverterProvider.class,
DefaultAttributeConverterProvider.class
})
public class Customer {
// Public bean properties and key annotations go here.
}CustomConverterProvider is your AttributeConverterProvider implementation; the default provider is in software.amazon.awssdk.enhanced.dynamodb. Make sure a custom converter can read existing stored values as well as write new ones. A Java v1 @DynamoDBTypeConverted annotation does not configure the v2 Enhanced Client.
See Java mapping and AWS documentation.
Other Common DynamoDB Errors (with Solutions)
- failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.
- DynamoDB Internal Server Error
- dynamodb cannot convert undefined to object
- DynamoDB Error 413
- why is the GSI dynamodb not showing item count
- dynamodb cannot assign requested address
- dynamodb query is null
- DynamoDB error 400
- dynamodb could not connect to the endpoint url
- dynamodb global secondary index does not project
- DynamoDB - The Security Token Included In The Request Is Invalid
- dynamodb query is not null
- DynamoDB local error unable to access JAR file dynamodblocal.jar
- dynamodb cannot read property '0' of undefined
- DynamoDB No Regionendpoint Or Serviceurl Configured
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase