Error: DynamoDB Not Supported Requires @DynamoDBTyped Or @DynamoDBTypeConverted

not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted comes from Java SDK 1.x DynamoDBMapper when it cannot map a property. This is a client mapping issue; DynamoDB itself supports document maps and lists.

1. Identify the getter and declared Java type named in the exception, including collection element types.
2. Use @DynamoDBTyped when the mapper supports the Java type but needs an explicit DynamoDB representation. It does not teach the mapper how to serialize any arbitrary class.
3. For a custom scalar representation, implement DynamoDBTypeConverter and attach @DynamoDBTypeConverted to the accessor. Test convert and unconvert with existing records.
4. For a nested document, consider @DynamoDBDocument on an appropriate bean. Ignore a property only when it should not be persisted.

Do not add annotations indiscriminately or convert every object to an opaque string. Choose a representation that supports the reads and expressions your application needs.

For current Java code, migrate to the v2 Enhanced Client. Its equivalents are a mapped bean or schema, AttributeConverter, and @DynamoDbConvertedBy. V1 and v2 annotations are different APIs and cannot be mixed to configure one mapper.

See Java mapping guidance and AWS documentation.

Enhanced Client converter configuration covers the current API.