zlacker

The Java SDK for SQS automatically drops >256k messages into an S3 bucket and stores a pointer to the message in SQS itself. You set the bucket and the client transparently handles retrieving a message from SQS/S3 when necessary.

Based on the structure of the message (UUIDv4) you could probably roll your own implementation in any language.

>>mark24+(OP)
That's a good idea, but wouldn't sending and later retrieving millions of S3 objects be expensive?

>>Jemacl+1y
Yes, and slow, if you're actually doing it for millions. The comment was saying the library only does it for messages that are over the size limit though.

>>maniga+ZD
Gotcha.