Dynatrace - TypeError on middlewareUserAgent on all versions >= 3.906.0

[victor-corja]

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

When we deploy containers that use AWS SDK versions above 3.901.0 for any client, we get an unresolved failure with the following error due to our Dynatrace agent:

TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
    at new (/src/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:9054:54)

This was not happening before that, and overriding the version to 3.901.0 resolves the issue, but that is not a scalable solution. The line above resolves specifically to
this.middlewareStack.use(middlewareUserAgent.getUserAgentPlugin(this.config));
for @aws-sdk/client-s3, but this line is present in all clients as it is shared.

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

"@aws-sdk/client-s3": "3.901.0", "@aws-sdk/client-ssm": "3.901.0"

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

Node 22

Reproduction Steps

I believe this happens during initialization:

export function init() {
    const region = process.env.AWS_REGION || process.env.REGION || 'us-east-1';
    client = new S3Client({ region });
}

Returning:

TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
    at Object.dynatraceRegularInvoke [as doInvoke] (/opt/dynatrace/oneagent/agent/bin/1.321.51.20250905-075429/any/nodejs/nodejsagent.js:3042:22)
    at Object.getUserAgentPlugin (/opt/dynatrace/oneagent/agent/bin/1.321.51.20250905-075429/any/nodejs/nodejsagent.js:12647:21)
    at new S3Client (/src/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:9054:54)

Observed Behavior

TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
    at Object.dynatraceRegularInvoke [as doInvoke] (/opt/dynatrace/oneagent/agent/bin/1.321.51.20250905-075429/any/nodejs/nodejsagent.js:3042:22)
    at Object.getUserAgentPlugin (/opt/dynatrace/oneagent/agent/bin/1.321.51.20250905-075429/any/nodejs/nodejsagent.js:12647:21)
    at new S3Client (/src/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:9054:54)

Expected Behavior

Successful initialization as with versions 3.901.0 and before.

Possible Solution

No response

Additional Information/Context

No response

[kuhe]

The stack trace says it happens in Dynatrace code. Could you show the JS source code for the top of the stack?

TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
    at Object.dynatraceRegularInvoke [as doInvoke] (/opt/dynatrace/oneagent/agent/bin/1.321.51.20250905-075429/any/nodejs/nodejsagent.js:3042:22)
    at Object.getUserAgentPlugin (/opt/dynatrace/oneagent/agent/bin/1.321.51.20250905-075429/any/nodejs/nodejsagent.js:12647:21)

I wasn't able to find it online and without it I cannot evaluate what is happening.

[jonataswalker]

Same (I guess) here

/opt/dynatrace/oneagent-paas/agent/bin/1.323.40.20250923-133428/any/nodejs/nodejsagent.js:3044
      return Reflect.apply(l, n, p);
                     ^
TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
    at new S3Client (/home/node/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:9054:54)
    at new S3 (file:///home/node/node_modules/@dw/shared/dist/entities/s3.js:19:23)
    at S3.getInstance (file:///home/node/node_modules/@dw/shared/dist/entities/s3.js:29:27)
    at new Storage (file:///home/node/node_modules/@dw/shared/dist/entities/storage.js:30:18)
    at Storage.getInstance (file:///home/node/node_modules/@dw/shared/dist/entities/storage.js:34:32)
    at file:///home/node/dist/entities.js:77:40
    at ModuleJob.run (node:internal/modules/esm/module_job:345:25)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

[jonataswalker]

3.901.0 working version

[kuhe]

could you open an issue with Dynatrace? I don't have enough information from the stack trace to diagnose the problem.

[h-line]

We are also having the same problem and Dynatrace in use. Dynatrace hasn't been updated. It seems the cjs build has been rewritten between a working and failing versions, could that affect instrumentation?

[h-line]

I also opened a ticket with Dynatrace. Waiting for their response.

[h-line]

Dynatrace verified that the issue is on their end and they are working on the fix. Meanwhile downgrading to working version would be the easiest workaround.

[h-line]

Dynatrace status and workaround (requires login) https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Upgrade-of-AWS-SDK-to-version-3-906-for-Node-js-causes-crashes/ta-p/287917

[tomw-dynatrace]

Hello Dynatrace users,
As indicated by @h-line (thank you!) we are aware of this issue present for customers upgrading to aws-sdk ≥ 3.906 for Node.js. We are actively working on a permanent solve as part of support for the newly released SDK version.

For more information and available workarounds while we work on a permanent fix, please consult the Dynatrace Community post or feel free to Contact support.

Thank you for your understanding!