Send SQS messages larger than 256 KB using the Amazon SQS Extended Client Library with S3

domain: docs.aws.amazon.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗

Verified steps

  1. Add the amazon-sqs-java-extended-client-lib dependency (or the equivalent Python/Node.js sqs-extended-client package) to your project
  2. Create an S3 bucket dedicated to storing large message payloads and grant the application's IAM role read/write access to it
  3. Configure an ExtendedClientConfiguration pointing at that bucket, wrapping your normal SQS client to produce an extended client
  4. By default, the extended client only offloads a message to S3 when its size exceeds the SQS 256 KB limit; optionally set alwaysThroughS3 to true to force every message through S3 regardless of size
  5. Send messages through the extended client as usual; it transparently uploads the payload to S3 and sends a small SQS message containing a reference (pointer) to the S3 object, up to a supported payload size of 2 GB
  6. On the consumer side, use the matching extended client to receive messages; it automatically resolves the S3 reference and returns the full payload, and can optionally delete the S3 object after successful processing

Known gotchas

Related routes

Manage AWS IoT Device Shadow within the 8 KB document size limit
docs.aws.amazon.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans