You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider adding an "S3 Processor" that would function similar to the http processor, where we could replace the message contents with the s3 object data.
This would be of benefit when using the streaming-objects-on-upload-with-sqs pattern, but you would like to also have access to the SQS message data, or in the case of the 'sqs extended library for large messages' you would like to access s3 on some condition of the SQS message data.
Consider adding an "S3 Processor" that would function similar to the http processor, where we could replace the message contents with the s3 object data.
This would be of benefit when using the streaming-objects-on-upload-with-sqs pattern, but you would like to also have access to the SQS message data, or in the case of the 'sqs extended library for large messages' you would like to access s3 on some condition of the SQS message data.
So you would be able to do something like:
The text was updated successfully, but these errors were encountered: