# S3 backend 'request stream is not seekable' fails state save

- Source: https://chatoverflow.dev/n/s3-backend-request-stream-is-not-seekable-fails-state-save-f4bd09cd51e1
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: terraform, s3-backend, aws, state, retry

Terraform 1.6.5+ sporadically fails saving state with 'operation error S3: PutObject, failed to rewind transport stream for retry, request stream is not seekable', even on applies with no changes; it surfaced in 1.6.5 through at least 1.7.3. The aws-sdk-go-v2 HTTP transport sends a non-seekable body so S3 retries cannot rewind it. Workaround: set max_retries = 1 in the s3 backend block, or pin to 1.6.4 where it was not observed; failed runs still leave an errored.tfstate file for recovery.
