Recursive s3 cp fails with "Need to rewind the stream <botocore.httpchecksum.AwsChunkedWrapper object at 0x10c8762b0>, but stream is not seekable."

[corneliusroemer]

Describe the bug

When doing recursive upload of around 8 files with multiple files of order 100MB I get upload errors:

$ aws s3 cp /Users/cr/Downloads/ \
  s3://nextstrain-ncov-private/gisaid-tars/unprocessed/ \
  --recursive \
  --exclude "*" \
  --include "gisaid_auspice_input_hcov-19_2026_01_27*.tar"

upload failed: Downloads/gisaid_auspice_input_hcov-19_2026_01_27_19 (4).tar to s3://nextstrain-ncov-private/gisaid-tars/unprocessed/gisaid_auspice_input_hcov-19_2026_01_27_19 (4).tar Need to rewind the stream <botocore.httpchecksum.AwsChunkedWrapper object at 0x10c8762b0>, but stream is not seekable.

Profile:

[profile default]
s3 =
  max_concurrent_requests = 200
  max_queue_size = 5000
  multipart_threshold = 4MB
  multipart_chunksize = 4MB

Regression Issue

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

Maybe a regression, I didn't see this error until today.

Expected Behavior

No error

Current Behavior

upload failed: Downloads/gisaid_auspice_input_hcov-19_2026_01_27_19 (4).tar to s3://nextstrain-ncov-private/gisaid-tars/unprocessed/gisaid_auspice_input_hcov-19_2026_01_27_19 (4).tar Need to rewind the stream <botocore.httpchecksum.AwsChunkedWrapper object at 0x10c8762b0>, but stream is not seekable.

Reproduction Steps

Can't share the files due to privacy.

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.33.7 Python/3.13.11 Darwin/25.2.0 source/arm64

Environment details (OS name and version, etc.)

Darwin/25.2.0 source/arm64

[adev-code]

Hello @corneliusroemer, thanks for reaching out. I have replicated the exact factors as stated above and I was able to upload all 8 files. I was not able to reproduce the issue, could you please provide full logs by adding --debug. Please redact any sensitive and security information.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.