> For the complete documentation index, see [llms.txt](https://docs.exavault.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exavault.com/installing-and-upgrading-the-appliance/installation-and-setup/aws-installation.md). # AWS Installation Installing the appliance on AWS has three stages: * Gather the prerequisites (a fully-qualified domain name and a static IP address). * Launch a new EC2 instance using the AMI. * Configure the settings in the Appliance Manager. ## Prerequisites Before installing the ExaVault appliance, confirm that you can provision a virtual appliance that meets our [System Requirements](/installing-and-upgrading-the-appliance/system-requirements.md) and that you can comply with our required [Firewall Configuration](/installing-and-upgrading-the-appliance/firewall-configuration.md). If you plan to use SSH to connect to your appliance, update your networking rules to allow inbound TCP 10022 from the addresses that will manage the appliance before starting. ### Networking Set a static (or rarely-changing) IP address because your installation's [license is associated with its IP address](/administration/license-keys.md#ip-address-changes). Frequent updates to the appliance's IP address will invalidate the license. You will need to know the internal IP address the appliance will use, along with the public IP address used for Network Address Translation (NAT). ### Domain Name ExaVault requires a fully qualified domain name (FQDN) set as the server's hostname. Avoid using `ftp` in the hostname because the appliance supports several protocols. A name such as `files.example.com` works well. ### SSL Certificate The appliance creates a self-signed certificate during installation. HTTPS and FTPS connections are encrypted with that certificate, but most clients cannot verify its issuer and display a warning. Plan to enable automatic SSL certificate management or install a certificate issued for your hostname by a trusted certificate authority. ## Launch the Instance ExaVault is published on the AWS Marketplace, and you can use the AWS Marketplace to launch an ExaVault server into your AWS account. [ExaVault on the AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-ak3rh6b5e5jue) The minimum supported instance sizes on AWS are `c5n.xlarge`, `m6i.xlarge`, or `m7i.xlarge`. A security group with the recommended network rules is included in the software. Launch the instance and wait a few minutes for it to initialize. Then open `https:///` in a web browser. When the appliance has initialized, it creates a self-signed SSL certificate, which may display a security warning in your browser. It is safe to instruct your browser to let you interact with the site so you can move on to configuration. ## Configure the Appliance ### Appliance Manager Password Create a password for the Appliance Manager and store it in an approved password manager. ### Registration After you have assigned a password, complete the form to register your appliance and create a free license. No payment information is required, and your contact information is stored securely. ### SSL Certificate The appliance creates a self-signed certificate during installation. It can operate with that certificate, but most clients display a trust warning. If you do not add a certificate during installation, use the Appliance Manager after setup to [install or configure one](/administration/installing-or-updating-an-ssl-certificate.md). ### Configuration After creating the license, the Appliance Manager displays its home page. Open *Configuration* and enter information about the network environment. * *Hostname*: The FQDN used to access the appliance, such as `files.example.com`. * *IP Address*: The appliance IP address that matches the hostname's DNS record. ExaVault uses it to handle FTP and SFTP through NAT. * *External FTP IP Address*: Usually the same as *IP Address*. Use the public address when a router forwards ports to a different internal appliance address. * *Email Host*: The SMTP server that delivers messages generated by the appliance. * *Email Port*: The port used to connect to the SMTP service. * *Email SSL*: Select this option when the SMTP service requires SSL, typically on port `465`. * *Email Username* and *Email Password*: The credentials used to authenticate with the SMTP service. * *Email From*: The From address used for messages generated by the appliance. ## Ready to Use Saving these configuration changes restarts the appliance. After the restart, verify the web interface and each enabled connection method before giving users access. ## Log In to the Web Interface Use a web browser to access your server at the address you configured for the appliance's hostname. Log in with the default username `administrator` and the password `password`. Change your password immediately upon logging in. The web interface is available at `https:///`. ## Other Connections Your [FTP and FTPS](/connection-methods/ftp-and-ftps.md) and [SFTP](/connection-methods/sftp.md#connection-settings) services are available through either the public IP address or domain name. Access the Appliance Manager at `https://:9002/`.