1-800-691-1991 | 9am - 8pm ET

Deploying Veeam Backup for Microsoft Office 365 Backup Proxy Server in AWS

KB ID: 3212
Product: Veeam Backup for Microsoft Office 365
Version: Any
Published: 2020-06-22
Last Modified: 2020-11-10


You need to configure an Amazon EC2 instance to act as a Backup Proxy for Veeam Backup for Microsoft Office 365 in AWS. For example, this may be required in of the following reasons:

  • Current proxy/deployment has or will reach configuration maximums.
  • Growth within the Organization(s).
  • You need to meet RPO requirements for Microsoft Office 365 backup by distributing backup load to multiple backup proxies.


The first step to add a Backup Proxy to an existing Veeam Backup for Microsoft Office 365 deployment in AWS is to deploy a new Windows Server EC2 instance with the appropriate settings for your design. Veeam Backup for Microsoft Office 365 requires a machine that runs a Windows x64 OS and has a minimum of 4 CPU cores and 8 GiB of RAM (c5.xlarge).

For Veeam Backup for Microsoft Office 365 system requirements, refer to the System Requirements section of the User Guide. For more information about sizing, refer to the
Sizing section of the Veeam Backup for Microsoft Office 365 Best Practices.
Once you have determined your instance size, complete the following steps:

  1. In the EC2 Management console, click Launch Instance.

  2. At the Choose an Amazon Machine Image (AMI) step, type "windows" in the search bar, choose Microsoft Windows Server 2019 Base for the instance type and click Select.

  3. At the Choose an Instance Type step, select the required instance type. In this example, the c5.xlarge type is used, but your instance type may be different depending on the needs determined above. Choose your instance type and click Next: Configure Instance Details.

  4. At the Configure Instance Details step, specify VPC and subnet settings. In some use cases, the default settings will be sufficient, and in others you will need to select the appropriate settings. Once you have specified the settings, click Next: Add Storage.

  5. At the Add Storage step, add a volume that will be used as a backup repository. Veeam Backup for Microsoft Office 365 Backup Proxy requires a data disk attached that will be used as a cache, while S3 will be used as a location where backup data is stored for long-term retention. The cache is stored in a JET database. For the best performance, it is recommended that st1 EBS volume is used. In general, the size of the EBS volume must be 10% of the source size. To add a volume, click Add New Volume and select the Volume Type. In this example, a 500 GB ST1 volume is used. Once you have added a volume that meets your specific needs, click Next: Add Tags.

    User-added image

  6. At the Add Tags step, you can add tags to the instance. Otherwise, click Next: Configure Security Group.

  7. At the Configure Security Group step, you have several choices to make. You can create a new Security group for this instance, or you can select an existing group. In this example, the instance is deployed in the same security group as the Veeam Backup for Microsoft Office 365 Server. If you choose a different security group, it is important to understand what ports must be opened to allow communication to and from the Veeam Backup for Microsoft Office 365 Server. Once you have selected an existing security group or created a new one with the required ports, click Review and Launch.

  8. Review the settings and click Launch.


Once the launch is complete, you can add the new instance as a Backup Proxy and Backup Repository on the Veeam Backup for Microsoft Office 365 Server.



KB ID: 3212
Product: Veeam Backup for Microsoft Office 365
Version: Any
Published: 2020-06-22
Last Modified: 2020-11-10

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.