Using Sentry breaks S3 put via @aws-sdk

Is there an existing issue for this?

I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
I have reviewed the documentation https://docs.sentry.io/
I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

^9.25.1

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

I am using this function to put onto s3:

export const s3put = async (key, val, options) => {
  const { acl, contentType } = options || {};
  const params = {
    Bucket: bucket,
    Key: key,
    Body: val,
    ContentType: contentType,
    ACL: acl,
  };

  try {
    await s3.send(new PutObjectCommand(params));
  } catch (e) {
    console.error('s3put got error:', e, params);
    throw e;
  }
  const url = s3url(key);
  return url;
};

Without Sentry, it works fine.

My Sentry instrument.js file is:

import * as Sentry_ from '@sentry/node';
export const Sentry = Sentry_;

if (process.env.ENV == 'prod') {
  Sentry.init({
    dsn: '...',
    sendDefaultPii: true,
  });
}

Expected Result

It should upload to s3

Actual Result

When I add Sentry instrumentation, I get this error:

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ClientRequest.setHeader (node:_http_outgoing:699:11)
    at SentryHttpInstrumentation._onOutgoingRequestCreated (/app/node_modules/@sentry/node/src/integrations/http/SentryHttpInstrumentation.ts:265:15)
    at onHttpClientRequestCreated (/app/node_modules/@sentry/node/src/integrations/http/SentryHttpInstrumentation.ts:167:12)
    at Channel.publish (node:diagnostics_channel:150:9)
    at new ClientRequest (node:_http_client:384:35)
    at request (node:https:381:10)
    at /app/node_modules/@smithy/node-http-handler/dist-cjs/index.js:366:19
    at new Promise (<anonymous>)
    at _NodeHttpHandler.handle (/app/node_modules/@smithy/node-http-handler/dist-cjs/index.js:300:12)
    at async /app/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:456:18 {
  code: 'ERR_HTTP_HEADERS_SENT'
}

I'm seeing exactly the same error, though with a slightly different stack trace:

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ClientRequest.setHeader (node:_http_outgoing:699:11)
    at SentryHttpInstrumentation._onOutgoingRequestCreated (file:///PrairieLearn/node_modules/@sentry/node/build/esm/integrations/http/SentryHttpInstrumentation.js:159:15)
    at onHttpClientRequestCreated (file:///PrairieLearn/node_modules/@sentry/node/build/esm/integrations/http/SentryHttpInstrumentation.js:61:12)
    at Channel.publish (node:diagnostics_channel:150:9)
    at new ClientRequest (node:_http_client:384:35)
    at request (node:https:381:10)
    at /PrairieLearn/node_modules/@opentelemetry/instrumentation-http/build/src/http.js:513:41
    at safeExecuteInTheMiddle (/PrairieLearn/node_modules/@opentelemetry/instrumentation/build/src/utils.js:28:18)
    at /PrairieLearn/node_modules/@opentelemetry/instrumentation-http/build/src/http.js:505:78
    at AsyncLocalStorage.run (node:internal/async_local_storage/async_hooks:91:14)
    at SentryContextManager.with (/PrairieLearn/node_modules/@opentelemetry/context-async-hooks/build/src/AsyncLocalStorageContextManager.js:33:40)
    at SentryContextManager.with (file:///PrairieLearn/node_modules/@sentry/opentelemetry/build/esm/index.js:1425:24)
    at ContextAPI.with (/PrairieLearn/node_modules/@opentelemetry/api/build/src/api/context.js:60:46)
    at outgoingRequest (/PrairieLearn/node_modules/@opentelemetry/instrumentation-http/build/src/http.js:496:38)
    at httpsOutgoingRequest (/PrairieLearn/node_modules/@opentelemetry/instrumentation-http/build/src/http.js:224:93)
    at /PrairieLearn/node_modules/@smithy/node-http-handler/dist-cjs/index.js:366:19 {
  code: 'ERR_HTTP_HEADERS_SENT'
}

I also believe this is related to S3, and the error definitely comes from Sentry internals.

This is probably a duplicate of #16438.

This should be fixed with fix(node): Ensure adding sentry-trace and baggage headers via SentryHttpInstrumentation doesn't crash #16473

Downgrading to 9.15.0 fixes this.

Downgrading to 9.15.0 fixes this.

Same problem also for us; we downgraded successfully to 9.22.0 (any version greater than this doesn't work).

We just released 9.26.0 which should fix this, please upgrade.

I can confirm that this fixed the issue for my applications. Thanks for the quick turnaround!

Navigation Menu

Repository navigation

Using Sentry breaks S3 put via @aws-sdk #16477

Is there an existing issue for this?

How do you use Sentry?

Which SDK are you using?

SDK Version

Framework Version

Link to Sentry event

Reproduction Example/SDK Setup

Steps to Reproduce

Expected Result

Actual Result

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Using Sentry breaks S3 put via @aws-sdk #16477

Description

Is there an existing issue for this?

How do you use Sentry?

Which SDK are you using?

SDK Version

Framework Version

Link to Sentry event

Reproduction Example/SDK Setup

Steps to Reproduce

Expected Result

Actual Result

Activity

nwalters512 commented on Jun 3, 2025

nwalters512 commented on Jun 3, 2025

RulaKhaled commented on Jun 4, 2025

strongpauly commented on Jun 4, 2025

federico-conte-79 commented on Jun 4, 2025

andreiborza commented on Jun 4, 2025

nwalters512 commented on Jun 4, 2025

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions