What is our primary use case?
Our main use case for bucket_av involves using the Scan on Access feature to scan files whenever they are accessed from our
S3 buckets, specifically files that are provided by our customers.
bucket_av works for our team in a fully transparent manner, as we are using the Scan on Access functionality which allows us to use the S3 bucket as if it were a normal S3 bucket.
It fits very nicely into our workflow and required no changes in our application code.
What is most valuable?
The Scan on Access feature of bucket_av stands out especially for us because we did not have to make any changes to our application code, which was already using an S3 bucket.
That is the main feature we are using; we are not using any other features at the moment.
bucket_av has positively impacted our organization by giving us confidence that the files we are handling do not contain any malware or anything of that nature, so it definitely brings benefits to our security posture.
What needs improvement?
bucket_av has actually added the features that we wanted within a couple of days, showing they were very responsive and helpful.
My experience working with their team has been great, as the response times have always been very short and they have always taken any input seriously and acted on it.
For how long have I used the solution?
We have been using bucket_av for about two years.
What do I think about the stability of the solution?
bucket_av is stable with zero downtime, but there was one incident when it did not seem to scan the files; however, restarting the nodes helped and that has happened only once in two years.
What do I think about the scalability of the solution?
bucket_av's scalability is perfect, as the autoscaling group seems to work just fine and handle all the traffic we can throw at it.
How are customer service and support?
The customer support for bucket_av is perfect, as they usually answer within thirty minutes of an email and always provide very clear answers to the questions that we have.
Which solution did I use previously and why did I switch?
In a different project, we used a self-hosted ClamAV solution, which required continuous instances and maintenance, so I switched to bucket_av because it just works on spot instances for us.
How was the initial setup?
It was very straightforward to deploy bucket_av in my environment with
Terraform, utilizing the
Terraform CloudFormation they provided.
My experience with the configuration process was mostly easy, though the only issue was that they changed the subnet feature somewhat, which resulted in some update failures, but other than that, it was very straightforward.
What was our ROI?
I have seen a return on investment, as in a previous project where we managed our own antivirus solution, it was quite a bit more work and required effort almost monthly, if not weekly, so bucket_av is clearly saving us time and the pricing is perfect.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for bucket_av was as expected with no surprises; it is a very cost-effective way to perform this task.
Which other solutions did I evaluate?
We discovered bucket_av and it was the most convenient option right away, so there was no need to look for anything else.
What other advice do I have?
My experience with the procurement process was easy.
It was really easy to buy bucket_av through the AWS Marketplace; I encountered no problems.
My thoughts about the metering and billing experience are positive, as bucket_av provides their own dashboard for the volumes and data usage, so it is fairly easy to see how much data is going through and the amount of money it costs.
My advice to others looking into using bucket_av is that if you want a bolt-on solution to scan S3s, I think it is a perfect solution if you do not want to modify your application code that is already using an S3 bucket.
I give this product a rating of five out of five.