Update Guide

If you don’t have an existing bucketAV installation, read the Setup Guide instead!

You can update bucketAV without downtime. An update can happen while files are scanned.

Update bucketAV

If you update from Version 1.x, read the Migration Guide first! Which version am I using?

  1. To update bucketAV, go to the AWS CloudFormation Management Console .
  2. Double-check the region at the top right.
  3. If you followed the Setup Guide, search for bucketav (or s3-virusscan for older installations), otherwise search for the name you specified.
  4. Select the stack and click on Update. Step 1
  5. Select Replace current template and provide an Amazon S3 URL from the following list based on your delivery method (aka fulfillment option):
    • Dedicated public VPC (recommended): https://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/39d58953-9c3f-4b5d-a00c-3df2aa282f32/e1448957a0554c35b894818930a0cc99.template Copy
    • Dedicated private VPC: https://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/39d58953-9c3f-4b5d-a00c-3df2aa282f32/617f96e2e9e54e3aa19475a7b9c3c297.template Copy
    • Existing VPC: https://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/39d58953-9c3f-4b5d-a00c-3df2aa282f32/1d285153b2f2406688eab8334a8ce9c1.template Copy Step 2
  6. Click on Next.
  7. Scroll to the bottom of the page and click on Next. Step 3
  8. Scroll to the bottom of the page and click on Next. Step 4
  9. Scroll to the bottom of the page, enable I acknowledge that AWS CloudFormation might create IAM resources, and click on Update stack. Step 5
  10. While the update runs, the stack status is UPDATE_IN_PROGRES. Reload the table from time to time and … Step 6
  11. … wait until the CloudFormation stack status switches to UPDATE_COMPLETE. Step 7

You are done!

Migration Guide

v1 to v2

  • The product was renamed from VirusScan for Amazon S3 to bucketAV - Antivirus for Amazon S3.
  • EC2 instances now run on spot capacity. Set the parameter CapacityStrategy to OnDemandOnly to launch on-demand instances as before (more expensive).
  • The parameter VolumeSize was removed. No action is needed.
  • The SNS message subject changed from s3-virusscan s3://${BUCKET_NAME} to bucketAV Scan Result for S3 Bucket ${BUCKET_NAME}. No topic subscriber should rely on the subject.
  • The parameter TagKey now defaults to bucketav (previously s3-virusscan) for new installations. You can change the default if needed.
  • If the parameter OpsCenterIntegration is set to true, the source in Ops Items changes from s3-virusscan to bucketAV.
  • Add-Ons
    • The parameter S3VirusScanStackName changed to BucketAVStackName.

v1.3 to 1.4

If you use bucketAV in a Multi-Account setup, please whitelist all accounts by adding them (comma separated) in the AWSAccountRestriction parameter.

Stay up-to-date

Get notified about security updates and new capabilities.