Resurfaced: DynamoDBDocument can't unmarshall null

[adclark1]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

If I'm not mistaken, it appears that the latest version of @aws-sdk/middleware-logger (released today) has caused the bug described in the following previously closed issues to resurface:

#3846
#4222

It's causing this error again when fetching items with null attributes using @aws-sdk/lib-dynamodb:

TypeError: Cannot read properties of null (reading 'S')

SDK version number

@aws-sdk/middleware-logger@3.287.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

Lambda nodejs16.x

Reproduction Steps

const { DynamoDBClient } = require('@aws-sdk/client-dynamodb');
const { DynamoDBDocumentClient, GetCommand } = require('@aws-sdk/lib-dynamodb');

const ddbClient = new DynamoDBClient();
const ddbDocClient = DynamoDBDocumentClient.from(ddbClient);

const response = await ddbDocClient.send(new GetCommand({
    TableName: 'table',
    Key: {
      pk: 'pk',
      sk: 'sk',
    },
  }));

Observed Behavior

TypeError: Cannot read properties of null (reading 'S')

{
    "errorType": "TypeError",
    "errorMessage": "Cannot read properties of null (reading 'S')",
    "stack": [
        "TypeError: Cannot read properties of null (reading 'S')",
        "    at AttributeValueFilterSensitiveLog (/var/task/test/node_modules/@aws-sdk/client-dynamodb/dist-cjs/models/models_0.js:1328:13)",
        "    at /var/task/test/node_modules/@aws-sdk/client-dynamodb/dist-cjs/models/models_0.js:1414:128",
        "    at Array.reduce (<anonymous>)",
        "    at GetItemOutputFilterSensitiveLog (/var/task/test/node_modules/@aws-sdk/client-dynamodb/dist-cjs/models/models_0.js:1414:40)",
        "    at /var/task/test/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:17:21",
        "    at processTicksAndRejections (node:internal/process/task_queues:96:5)",
        ...
    ]
}

Expected Behavior

Successful retrieval of item with a null attribute without an error being thrown.

Possible Solution

No response

Additional Information/Context

Seeing this with the latest version of @aws-sdk/client-dynamodb and @aws-sdk/lib-dynamodb being used. It appears to be the dependencies they have on @aws-sdk/middleware-logger.

[yenfryherrerafeliz]

Hi @adclark1, sorry you are having this issue. I can confirm that this is a bug and I will push to have a fix soon. In the meantime please set logger to undefined when instancing the client, and it will prevent the error from happening.
Example:

import { DynamoDBClient } from '@aws-sdk/client-dynamodb';
import { DynamoDBDocumentClient, GetCommand } from '@aws-sdk/lib-dynamodb';

const ddbClient = new DynamoDBClient({
    region: 'us-east-2',
    logger: undefined // HERE
});
const ddbDocClient = DynamoDBDocumentClient.from(ddbClient);

const response = await ddbDocClient.send(new GetCommand({
    TableName: 'test-table',
    Key: {
        id: 'someid'
    },
}));
console.log(response)

Thanks!

[adclark1]

Good to know. Thanks!

[oyatrides]

Hello, I'm having this problem as well on "@aws-sdk/client-dynamodb": "^3.287.0", "@aws-sdk/lib-dynamodb": "^3.287.0"
Runtime : nodejs18.x
Logger used: "@aws-lambda-powertools/logger": "^1.5.1"

Using the logger: undefined workaround in the meantime. Just posting a comment to share my versions numbers.
Thank you for the hard work!

[kuhe]

this was fixed in #4502, it should release today in approximately 4 hours.