Traces disappeared after update to aws-sdk@v3 on EKS

[HemersonDock]

Expected behaviour

Actual behaviour

Steps to reproduce

After an upgrade from aws-sdk@v2 to aws-sdk@v3, most of traces like, dynamo-db, sqs, sns and other from aws services disappeared.

Note: Using aws-sdk@v3 in serverless applications, like lambda, all the services are displayed in traces normally. In serverless case we use a layer in our lambda and its version is .87.

Environment

• Operation system: Ubuntu 18.04
• Node.js version: node:16-alpine
• Tracer version: 3.15.0
• Agent version: 7.43.0
• Relevant library versions:

"dependencies": {
    "@aws-sdk/client-dynamodb": "3.254.0",
    "@aws-sdk/client-secrets-manager": "3.238.0",
    "@aws-sdk/client-sns": "3.241.0",
    "@aws-sdk/client-sqs": "3.252.0",
    "@aws-sdk/node-http-handler": "3.226.0",
    "@aws-sdk/util-dynamodb": "3.256.0",
    "dd-trace": "^3.15.0",
    "http-status-codes": "^2.2.0",
    "sqs-consumer-v3": "^1.0.0",
    "winston": "^3.3.3"
},

[Senney]

:+1: We've also observed that traces are no longer appearing for any AWS service once we upgrade to v3 of aws-sdk. Running in ECS Fargate tasks using a similar setup.

Operation system: Alpine Docker Node.js version: node:18-alpine Tracer version: 4.8.1