Unsure what to do with some aws-s3-virusscan alerts about aws-s3-virusscan HOT 4 CLOSED

My apologies. I got pulled into an end of year push on other projects that I'm just finished up with and have time to dig into this again. We're still having the dead letter queue problem and at this point we have 227 items in the queue. I looked at the CloudWatch logs and I'm not seeing anything that indicates that the messages can't be processed but I don't know which log I should be looking in or what a typical message indicating a failure to process a log would be.

So a few questions/requests.

• What is the best way to see the messages in the dead letter queue?
• Can we be notified of the specific S3 object that is stuck in the dead letter queue? Right now if an file is received but is not able to be processed I expect we have to dig through the DLQ to find it and remove it. It would be nice if this was automated but this is probably something that the end users can do. Even better would be if there was an option to delete both the problematic S3 object and the item in the queue.
• What is the best way to clear out the messages in the dead letter queue?

Different question entirely. Right now we're not automatically deleting infected files. Is there a way to enable that without rebuilding the whole CloudFormation stack? It's not too much trouble to rebuild the CloudFormation stack but it sure would be nice to be able to flip that bit rather than tearing it all down.

Thanks again for any assistance on this and my long delay getting back to you on this. I'm doing a lot of heads down work over the next few weeks so I'll be able to get back to you quickly if you need any information from me.

Best,
Kevin

from aws-s3-virusscan.

@kevinm Could you check CloudWatch Logs for errors? Looks like a file could not be scanned.

from aws-s3-virusscan.

is this still relevant?

from aws-s3-virusscan.

you can go to the SQS Service in the management console to look at the messages and purge all messages.

from aws-s3-virusscan.