There are areas that should be improved, such as user interface and visibility. Currently, most workflows rely on CloudWatch logs and Lambda triggers, which are technical. A more user-friendly dashboard showing scan results, quarantined files, and compliance status would make monitoring easier for non-technical staff. Additionally, performance metrics should be enhanced. While scanning is efficient, there is limited visibility into scan times, throughput, and resource usage. Adding performance analytics would help our teams optimize workflows and prove efficiency during audits. Granular controls represent another area for improvement. The current scanning policies apply bucket-wide. More fine-grained controls, such as scanning only certain file types, prefixes, or user uploads, would reduce unnecessary scans and improve efficiency. Performance visibility should also be enhanced. While scanning is stable, there is limited visibility into scan times, throughput, and resource usage. Adding performance analytics would help optimize workflows and prove efficiency during audits.
Antivirus for Amazon S3 is very stable now, and I do not want any changes. I did not want anything to be improved regarding Antivirus for Amazon S3. I did not want anything to be changed with Antivirus for Amazon S3. Everything is very good.
Sr. Enterprise Architect at a educational organization with 501-1,000 employees
Real User
Top 5
Apr 26, 2026
I think typically on the signed URLs, if they can do something such as when someone puts an object into the bucket, they can immediately do a scan of that object without the user or the organization having to ask for a scan. That will be very useful for any specific case, it could be a virus in itself or a trojan or any of those things. If it can immediately block that storage or immediately create an alert that they are quarantining it, that would be another great feature. If they can put a quarantine for any object that can be a little dodgy or can be a suspicious object being stored in that bucket, that could be a great feature to have. I think reporting does exist already with Antivirus for Amazon S3. We can generate those reports via CloudTrail but if they are integrated with the antivirus itself without us having to create specific reports every time would be better. In some cases generating those logs can be a little tedious. If they can be made easy and probably with some drag and drop feature, that will be really useful.
I would definitely say that if the solution gets updated on a day-to-day basis so that the cloud signature gets updated for all AWS account holders during the scanning, and if the deployment of updates happens every day, it would be helpful. Additionally, if AI and machine learning can be used in detecting and identifying algorithms to quickly identify malicious files across the storage locations and storage paths, it would really help enhance the solution.There are no major issues, but if the company could work on deployment features as well as cost-effectiveness and some specific features that require licensing needs, it would be really helpful.
One limitation I have identified is that advanced customizations can be tricky with fully managed solutions for Antivirus for Amazon S3. Sometimes we need more control over scanning logic or workflows. For needed improvements, I would say documentation is good, but troubleshooting scan failures or false positives can still take time with Antivirus for Amazon S3. Better debugging tools would help. One area I would like to see improved for Antivirus for Amazon S3 is the automation of certain security protocols, such as automatic updates and patch management to further enhance our security posture. I believe this would help us streamline our operations and reduce the risk of human error.
Antivirus for Amazon S3 could be improved by addressing that it is a little bit complicated to set up because you have to deploy it via CloudFormation or Terraform, and it can be a little bit difficult trying to troubleshoot the image or container issues. I have definitely found that. The error logs also are not always the clearest, so it does take a bit of a learning curve. The CloudWatch logs could also be better; I have noticed it streams them to different CloudWatch log streams, so it can be difficult to consolidate that data together. If you had a lot of data that generated many different logs, that could be quite difficult and time-consuming.
The reporting part could be a bit more detailed. A summary of all the scans in a better way would be beneficial. This part could be improved or enhanced.
DevOps Engineer at a tech vendor with 1,001-5,000 employees
Real User
Top 10
Dec 17, 2025
I think Antivirus for Amazon S3 can be improved by including patches over time and adding forensic analysis of data to show where viruses may have been incorporated. In future updates of Antivirus for Amazon S3, threat intelligence or forensic malware analysis would be beneficial.
I think Antivirus for Amazon S3 could be improved by slightly further automating the process; beyond just the ability to send notifications, if an email could be crafted or if communication through any channel could be established with the person or team who uploaded the file, that level of automation could be avoided on our end, allowing us to configure an entire loop from detecting a malicious upload to contacting the uploader and taking corrective action, which I think would be really cool.
Antivirus for Amazon S3 offers event-driven scanning and automated object tagging, enhancing security for files uploaded to S3 buckets with real-time threat detection.Enterprises find value in Antivirus for Amazon S3's ability to automate malware scanning upon file upload, integrating seamlessly with AWS tools. With real-time threat detection and multi-engine support, it minimizes manual tasks and improves the security posture. Vital for compliance, the solution efficiently streamlines...
There are areas that should be improved, such as user interface and visibility. Currently, most workflows rely on CloudWatch logs and Lambda triggers, which are technical. A more user-friendly dashboard showing scan results, quarantined files, and compliance status would make monitoring easier for non-technical staff. Additionally, performance metrics should be enhanced. While scanning is efficient, there is limited visibility into scan times, throughput, and resource usage. Adding performance analytics would help our teams optimize workflows and prove efficiency during audits. Granular controls represent another area for improvement. The current scanning policies apply bucket-wide. More fine-grained controls, such as scanning only certain file types, prefixes, or user uploads, would reduce unnecessary scans and improve efficiency. Performance visibility should also be enhanced. While scanning is stable, there is limited visibility into scan times, throughput, and resource usage. Adding performance analytics would help optimize workflows and prove efficiency during audits.
Antivirus for Amazon S3 is very stable now, and I do not want any changes. I did not want anything to be improved regarding Antivirus for Amazon S3. I did not want anything to be changed with Antivirus for Amazon S3. Everything is very good.
I think typically on the signed URLs, if they can do something such as when someone puts an object into the bucket, they can immediately do a scan of that object without the user or the organization having to ask for a scan. That will be very useful for any specific case, it could be a virus in itself or a trojan or any of those things. If it can immediately block that storage or immediately create an alert that they are quarantining it, that would be another great feature. If they can put a quarantine for any object that can be a little dodgy or can be a suspicious object being stored in that bucket, that could be a great feature to have. I think reporting does exist already with Antivirus for Amazon S3. We can generate those reports via CloudTrail but if they are integrated with the antivirus itself without us having to create specific reports every time would be better. In some cases generating those logs can be a little tedious. If they can be made easy and probably with some drag and drop feature, that will be really useful.
I would definitely say that if the solution gets updated on a day-to-day basis so that the cloud signature gets updated for all AWS account holders during the scanning, and if the deployment of updates happens every day, it would be helpful. Additionally, if AI and machine learning can be used in detecting and identifying algorithms to quickly identify malicious files across the storage locations and storage paths, it would really help enhance the solution.There are no major issues, but if the company could work on deployment features as well as cost-effectiveness and some specific features that require licensing needs, it would be really helpful.
One limitation I have identified is that advanced customizations can be tricky with fully managed solutions for Antivirus for Amazon S3. Sometimes we need more control over scanning logic or workflows. For needed improvements, I would say documentation is good, but troubleshooting scan failures or false positives can still take time with Antivirus for Amazon S3. Better debugging tools would help. One area I would like to see improved for Antivirus for Amazon S3 is the automation of certain security protocols, such as automatic updates and patch management to further enhance our security posture. I believe this would help us streamline our operations and reduce the risk of human error.
Antivirus for Amazon S3 could be improved by addressing that it is a little bit complicated to set up because you have to deploy it via CloudFormation or Terraform, and it can be a little bit difficult trying to troubleshoot the image or container issues. I have definitely found that. The error logs also are not always the clearest, so it does take a bit of a learning curve. The CloudWatch logs could also be better; I have noticed it streams them to different CloudWatch log streams, so it can be difficult to consolidate that data together. If you had a lot of data that generated many different logs, that could be quite difficult and time-consuming.
The reporting part could be a bit more detailed. A summary of all the scans in a better way would be beneficial. This part could be improved or enhanced.
I think Antivirus for Amazon S3 can be improved by including patches over time and adding forensic analysis of data to show where viruses may have been incorporated. In future updates of Antivirus for Amazon S3, threat intelligence or forensic malware analysis would be beneficial.
I think Antivirus for Amazon S3 could be improved by slightly further automating the process; beyond just the ability to send notifications, if an email could be crafted or if communication through any channel could be established with the person or team who uploaded the file, that level of automation could be avoided on our end, allowing us to configure an entire loop from detecting a malicious upload to contacting the uploader and taking corrective action, which I think would be really cool.