service · inferred from evidence

S3

AWS Simple Storage Service, a hosted object storage service.

Prediction interrupted; please retry (code: PA) when passing a file object as input
The `(code: PA)` interruption on file inputs happens when the file is too large to send inline, since the client base64-encodes it into the request body and the API caps request size. Upload the file somewhere reachable, a signed S3 URL wor
supporting2026-09-24 13:27 UTC
input_images must be a zip file error when running a training with a file handle
The `input_images must be a zip file` error on a valid zip comes from the client not passing the filename when you give it an open file handle, which broke the model's `.zip` extension check. Upgrade to replicate-python 0.32.1 or later, whi
supporting2026-09-23 21:16 UTC
OpenSearch 3.x snapshot repository fails on S3-compatible storage: "trailing checksum is not supported"
The 3.0.0 repository-s3 plugin's newer AWS SDK sends trailing checksums that S3-compatible stores reject. Verified workaround (confirmed by multiple users): set legacy MD5 checksum calculation per repository via the create-repository API, e
supporting2026-09-23 15:36 UTC
mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection
Two things came out of the thread. First, the immediate `syntax error at or near "ENDPOINT"` was just a missing comma: ENDPOINT has to be comma-separated from the previous clause, like REGION. ```sql CREATE SECRET ( TYPE S3, KEY_ID '..
supporting2026-09-23 15:35 UTC
Supabase Storage S3 API: AWS Go SDK v2 uploads fail with 403 SignatureDoesNotMatch
This was a Supabase-side S3 signature compatibility bug with the Go SDK v2's signing format. Maintainer itslenny confirmed on the thread that it is fully resolved in production, so the latest SDK works without any workaround. Before the fix
supporting2026-09-23 13:13 UTC
Textract rejects local PDFs: `Exception: PDF must be in S3 bucket`
The Textract async API (which is what multi-page PDFs need) only accepts documents stored as S3 objects — local files are rejected with exactly that exception. So the standard answer is: upload the PDF to an S3 bucket first, then pass the S
primary2026-09-23 12:01 UTC
aws-lambda-nodejs deploy fails: Uploaded file must be a non-empty zip
An empty zip for the asset got cached in the CDK bootstrap bucket. Delete the asset file for that function from the bootstrap S3 bucket and redeploy, which forces CDK to re-upload a fresh zip; a maintainer suggested exactly this. Several re
supporting2026-09-23 11:58 UTC

Skills in this topic

Backblaze B2 S3 endpoint rejects master keys; use an application key
Shows how to fix backblaze B2 S3 endpoint rejects master keys; use an application key. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
resolving dependency outputs: NoSuchBucket: The specified bucket does not exist
Fixes Terragrunt's dependency-output fetch failing with NoSuchBucket when the state bucket doesn't exist yet. Use when validate or plan with --dependency-fetch-output-from-state fails resolving a dependency instead of using mock_outputs. No
Error: could not create stack: the stack is currently locked by 1 lock(s)
Fixes Pulumi stack creation failing because a stale lock from a crashed process still exists. For platform teams on S3 backends (often via the Kubernetes operator) who see the lock error with no active run.
Error: passphrase must be set with PULUMI_CONFIG_PASSPHRASE (on a KMS-encrypted stack)
Fixes Pulumi demanding a passphrase on a stack that uses AWS KMS for secrets. For teams on S3 backends whose CI suddenly asks for PULUMI_CONFIG_PASSPHRASE, the cause is the local stack YAML losing its KMS metadata.
mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection
Shows how to fix mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Error: state data in S3 does not have the expected content: corrupt state object
Fixes Terraform's "Error: state data in S3 does not have the expected content" when the state object is corrupt or not actually state. Use when plan/apply fails reading a previously working S3 backend. Restore from S3 versioning; as a last
Tigris is 90% S3: check the unsupported list first
Switching from S3 to Tigris is an endpoint, region, and credentials change for most workloads.
sst deploy interrupted with no error: hard-reset the state snapshot in S3
Shows how to fix sst deploy interrupted with no error: hard-reset the state snapshot in S3. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
PlayHT integration limits: no SSML, engine tradeoffs, and S3-format voice IDs
When integrating PlayHT: strip SSML yourself before sending text, the API will silently drop the tags.
cdktf synth fails with "jsii.errors.JSIIError: Missing required properties" for a resource config block
Explains the CDKTF synth-time JSIIError raised when a nested configuration block is missing a required property (e.g. applyServerSideEncryptionByDefault on an S3 encryption rule). Shows how to read the error, find the required property in t
Polly long text: switch to the async task at 6000 characters
Synthesizing long-form audio with Polly: anything over 6000 characters (3000 billed) fails SynthesizeSpeech with TextLengthExceededException, so switch to StartSpeechSynthesisTask for documents and chapters.
Pinecone workflow: bulk import from S3, GCS, or Azure Blob
For very large datasets, skip the upsert API and import Parquet files directly from object storage. Stage the files, create the import, poll to completion. Not the full reference manual.
Terraform workflow: migrate state from local to a remote S3 backend
Moving from terraform.tfstate on disk to shared remote state is a one-way door if done wrong. The ordered runbook: backup, add backend, migrate, verify, then delete the local file.
Announcement: S3 default integrity change
Fixes XAmzContentSHA256Mismatch failures after boto3 1.36.0 enabled default S3 integrity checksums, by pinning back to boto3<1.36.0 as a stopgap or upgrading and keeping checksums on. Use when PutObject calls start failing after a boto3 upg
Prediction interrupted; please retry (code: PA) when passing a file object as input
Fixes 'Prediction interrupted; please retry (code: PA)' on Replicate when passing a file object by uploading the file to a URL (a signed S3 URL works for private files) and passing the URL instead. Use when replicate.run fails on local file