--- title: "Deploying virtual File Protect appliances on Amazon Web Services (AWS)" slug: "deploying-virtual-file-protect-appliances-on-amazon-web-services-aws" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-08-20T07:20:44Z published: 2026-09-09T22:45:46Z canonical: "docs.trellix.com/deploying-virtual-file-protect-appliances-on-amazon-web-services-aws" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploying virtual File Protect appliances on Amazon Web Services (AWS) An AMI (Amazon Machine Image) is a template that contains the software configuration needed to deploy a virtual File Protect appliance (known as an *instance* in AWS). The software configuration includes the operating system, application server, and applications that are needed to launch the instance. The File Protect instance can scan Amazon S3 buckets. The following table summarizes the steps to launch a File Protect instance in Amazon Web Services (AWS). ### Note This document provides the basic steps for launching Trellix virtual appliances, and assumes familiarity with launching virtual machines in AWS. For comprehensive information, see the AWS documentation provided by Amazon. | Task | Description | | --- | --- | | **1**. Launch the instance. | Some settings are defined by your system administrator. Other settings are required for the File Protect instance. For instructions, see [Launching a File Protect instance on AWS](/docs/launching-a-file-protect-instance-on-aws). | | **2**. *(Optional)* Apply the activation code and configure the initial admin password for the appliance. | See [Configuring the activation code and initial Admin password](/docs/configuring-the-activation-code-and-initial-admin-password-3). | | **3**. *(If using a static IP address for the ether1 interface)* Configure the IP address. | See [Configuring a static IP address for the ether1 interface](/docs/configuring-a-static-ip-address-for-the-ether1-interface-3). ### Note This step is required if you use a static IP address for the interface. If you use DHCP instead, make sure the lease is persistent to maintain the connection with the managed appliances. | | **4**. Perform the initial configuration of the appliance. | See [Performing the initial File Protect configuration using AWS](/docs/performing-the-initial-file-protect-configuration-using-aws). ### Caution In the "Primary IP address and masklen?" step of the configuration jump-start wizard, enter the same values you configured when you launched the instance on AWS. | | **5**. *Optional*: If you determine your instance is too small or too large for your needs, you can change the instance type. | [Changing an AWS instance type](/docs/changing-an-aws-instance-type) | :