Migration Guide

bucketAV comes in two variants: bucketAV powered by Sophos® and bucketAV powered by ClamAV®. This guide explains how to migrate from bucketAV powered by ClamAV® to bucketAV powered by Sophos® and vice versa.

Migration is possible at any time and without interrupting operations.

Migrating from bucketAV powered by ClamAV® to bucketAV powered by Sophos® (#)

To better estimate the costs of bucketAV powered by Sophos®, you can visit the dashboard to understand the amount of scanned data.

Start with subscribing to bucketAV powered by Sophos® through the AWS Marketplace.

  1. Open bucketAV powered by Sophos® in the AWS Marketplace.
  2. Click the Continue to Subscribe button.
  3. Press the Accept Terms button.
  4. The subscription is now Pending.
  5. Wait until the subscription becomes active.

Do NOT proceed the AWS Marketplace flow by clicking the Continue to Configuratio button.

Next, migrate your installation of bucketAV.

  1. Open the AWS CloudFormation service in the AWS Management Console.
  2. Double-check, that the correct region is selected (see main navigation top right).
  3. Navigate to Stacks.
  4. Select the bucketAV stack (if you followed the docs, the name is bucketav).
  5. Click on the Outputs tab.
  6. The output Engine shows the current engine of bucketAV. The value should be clamav. In case the output Engine is not avialble, you are running clamav as well.
  7. The output Version shows the current version of bucketAV. Remember the value.
  8. The output FulfillmentOption shows the fulfillment option. Remember the value.

Afterwards, pick the Amazon S3 URL of the matching CloudFormation template from the following table.

Fulfillment OptionAmazon S3 URL
dedicated-public-vpchttps://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/2b307b6c-8135-4f39-a086-880f7f3ed25e/01e7a05b1f7d47f0a91073b1b9125362.template Copy
dedicated-private-vpchttps://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/2b307b6c-8135-4f39-a086-880f7f3ed25e/e74d5dc2da174cb8b1ea00194f19c1af.template Copy
shared-vpchttps://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/2b307b6c-8135-4f39-a086-880f7f3ed25e/1df9565dac184870935cfe578ec26c19.template Copy

In case the current version is 1.x, follow the Migration Steps in the Update Guide first!

You are ready to migrate to bucketAV powered by Sophos®.

  1. Select the bucketAV stack (e.g., bucketav) and press the Update button. Step 1
  2. Select Replace current template and paste the Amazon S3 URL that you picked above. Step 2
  3. Click on Next.
  4. Scroll to the bottom of the page and click on Next. Step 3
  5. Scroll to the bottom of the page and click on Next. Step 4
  6. Scroll to the bottom of the page, select I acknowledge that AWS CloudFormation might create IAM resources, and click the Update stack button. Step 5
  7. While the update runs, the stack status is UPDATE_IN_PROGRES. Reload the table from time to time and … Step 6
  8. … wait until the CloudFormation stack status switches to UPDATE_COMPLETE. Step 7

You are now running bucketAV powered by Sophos®.

Migrating from bucketAV powered by Sophos® to bucketAV powered by ClamAV® (#)

Start with subscribing to bucketAV powered by ClamAV® through the AWS Marketplace.

  1. Open bucketAV powered by ClamAV® in the AWS Marketplace.
  2. Click the Continue to Subscribe button.
  3. Press the Accept Terms button.
  4. The subscription is now Pending.
  5. Wait until the subscription becomes active.

Do NOT proceed with the AWS Marketplace flow by clicking the Continue to Configuration button.

Next, migrate your installation of bucketAV.

  1. Open the AWS CloudFormation service in the AWS Management Console.
  2. Double-check, that the correct region is selected (see main navigation top right).
  3. Navigate to Stacks.
  4. Select the bucketAV stack (if you followed the docs, the name is bucketav).
  5. Click on the Outputs tab.
  6. The output Engine shows the current engine of bucketAV. The value should be sophos.
  7. The output FulfillmentOption shows the fulfillment option. Remember the value.

Afterwards, pick the Amazon S3 URL of the matching CloudFormation template from the following table.

Fulfillment OptionAmazon S3 URL
dedicated-public-vpchttps://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/39d58953-9c3f-4b5d-a00c-3df2aa282f32/4a31212aba52432a975497bb066dfa48.template Copy
dedicated-private-vpchttps://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/39d58953-9c3f-4b5d-a00c-3df2aa282f32/adf3232f98d44f37b5f44884fe72aa4d.template Copy
shared-vpchttps://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/39d58953-9c3f-4b5d-a00c-3df2aa282f32/07b6e87d4421438091331110067c5778.template Copy

You are ready to migrate to bucketAV powered by ClamAV®.

  1. Select the bucketAV stack (e.g., bucketav) and press the Update button. Step 1
  2. Select Replace current template and paste the Amazon S3 URL that you picked above. Step 2
  3. Click on Next.
  4. Scroll to the bottom of the page and click on Next. Step 3
  5. Scroll to the bottom of the page and click on Next. Step 4
  6. Scroll to the bottom of the page, select I acknowledge that AWS CloudFormation might create IAM resources, and click the Update stack button. Step 5
  7. While the update runs, the stack status is UPDATE_IN_PROGRES. Reload the table from time to time and … Step 6
  8. … wait until the CloudFormation stack status switches to UPDATE_COMPLETE. Step 7

You are now running bucketAV powered by ClamAV®.

Stay up-to-date

Monthly digest of security updates, new capabilities, and best practices.