Files not being scanned and deleted about aws-s3-virusscan HOT 10 CLOSED

Are there any messages in the SQS queue or dead-letter-queue?

from aws-s3-virusscan.

No, both queues are empty. I also made sure to check they were empty before I uploaded the files

from aws-s3-virusscan.

Could you please check the NumberOfMessagesReceived metric of your SQS queue? Did the queue receive any messages? If not, could you please verify that your S3 Event Notifications is correct?

from aws-s3-virusscan.

It looks like there were a few messages received by the queue around the time of the upload.

Furthermore, the SNS NumberOfNotificationsDelivered for that time period is 0. So although the queue may have been notified of the upload, the service either did not scan or did not recognize the malware

from aws-s3-virusscan.

Hi @ldel10
To reproduce the error, can you share the values of the CloudFormation parameter of the stack?

from aws-s3-virusscan.

I did not enter any parameter while creating the stack. The documentation implied that the two templates would handle the set up of all the proper resources

from aws-s3-virusscan.

@michaelwittig are there recommended parameters to use for stack creation? There was nothing in the documentation indicating that parameters are required

from aws-s3-virusscan.

@michaelwittig
The parameters for the first stack which sets up the vpc and the routing:

The parameters for my second stack for the queues and ec2 instances:

from aws-s3-virusscan.

Most parameters have default values. If you do not change them you use the default values (this is what you did). What we know is that you used the default values and it was not working for you. A stack with the default values is automatically created every 7 days to verify that the solution is still working. So I suspect that you are running in less obvious issues.

Since you closed the issue, is it resolved? If yes, could you share the cause of your issue?

from aws-s3-virusscan.

The issue is resolved. Interestingly, it started working after restarting the EC2 instance. Thank you for your help

from aws-s3-virusscan.