This is an archive version of the document. To get the most up-to-date information, see the current version.

Licensing

Veeam Backup for AWS is licensed per protected EC2 instance. An EC2 instance is considered protected if it has a restore point (cloud-native snapshot or image-level backup) created in the past 31 days. Each protected EC2 instance consumes 1 license unit. Note, however, that EC2 instances that are backed up only by manually created snapshots do not consume license units.

Product Editions

Veeam Backup for AWS is available in 3 editions:

  • Free

Veeam Backup for AWS operating in the Free edition allows you to protect up to 10 EC2 instances.

  • Paid

Veeam Backup for AWS operating in the Paid edition allows you to protect an unlimited number of EC2 instances.

In the Paid edition of the product, you are charged by AWS for EC2 instances that you actually protect. To track data protection operations on the backup server, Veeam Backup for AWS uses the AWS Marketplace Metering Service. Every hour, the backup server sends information on the current number of protected EC2 instances to AWS. The price for protected EC2 instances is included into the monthly AWS Cost and Usage report.

  • BYOL (Bring Your Own License)

Veeam Backup for AWS operating in the BYOL edition allows you to use a Veeam Backup for AWS license with a certain number of license units to protect EC2 instances.

For details on how to obtain the license, contact a Veeam sales representative at Sales Inquiry. For details on how to install the license on the backup server, see Installing and Removing License. Note that if the license is not installed, Veeam Backup for AWS operates in the Free edition and you can still protect up to 10 EC2 instances.

Licensing Tip:

If you used the Free edition of the product for evaluation and testing purposes and want to switch to any of the commercial editions without reconfiguring the backup infrastructure, follow the steps described in this Veeam KB article.

In This Section

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.