Question & suggestion

Is there any plan to bring the extended client in line with the standard client and produce an async version (or is this not possible due to the interactions with s3)?

It would be helpful if I could configure the client not to delete the s3 component of the message on the message delete action. This would then leave me an audit log of all the messages I'd received and I could then use the life-cycle attribute of the bucket to clear out the older messages that I no longer wish to retain.

Thanks,

Tim