[lazerg]

Why: DynamoDB calls made outside any active span each became their own root span with no context. The aws-sdk integration now skips the span for DynamoDB when there is no active span. Other services keep their current behavior, since a root producer span can be valid for S3, SQS, SNS or Lambda.

How to review: The fix is the early return in aws-sdk/index.ts. The new scenario runs PutItem before, inside and after a parent span and checks that only the one inside creates a span, on both aws-sdk versions the suite covers.

Closes #25801

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b1a3b32. Configure here.}

[nicohrubec]

after some more internal discussion on the approach for this I'll close this down as superseded by #25879