> For the complete documentation index, see [llms.txt](https://docs.zmanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zmanda.com/zmanda-classic/installation-and-configuration/step-1-install-zmanda-server/aws-marketplace-installation.md).
# AWS Marketplace Installation
Building Zmanda on AWS infrastructure enables you to deploy a backup server in any geography in a few minutes. It's also the ideal installation if your workloads are primarily in AWS instances. To begin, we log in to our AWS console and build a new instance via the Zmanda backup server image, available in the AWS marketplace. Below are the detailed steps.
1. Log in to the AWS management console using your credentials.
2. Click on the **Services** tab at the top navigational bar. You will find **EC2** under the Compute category of the Services tab. Click on **EC2** to open the EC2 dashboard.
3. Within the EC2 dashboard, you will see the Resources category right at the top. Click on the **Instances (running)** under the Resources category.
4. You will be presented with the instances screen. You can start the instance creation by clicking the **Launch instances** button at the top right corner of the screen.
5\. Enter the Names in the field provided under the names and tags section. You can click on **Add additional tags** to add additional tags if needed.
6\. Under the Application and OS Images (Amazon Machine Image) category, search for Zmanda via the search bar.
7\. Select the **AWS Marketplace AMIs** tab under the search results to see **Zmanda Enterprise Backup Server** as shown above and click on Select for **Zmanda Enterprise Backup Server**.
8\. Follow onscreen instructions till you reach the instance type dropdown. You can choose a suitable Instance type from the dropdown based on your need. Please note that t3a.medium is the bare minimum for the Zmanda backup server. You can select other instance types that offer more resources as well.
9\. The next step would be defining the Inbound security group rules, which would open the VMs ports. This would allow Zmanda to communicate with the target workload
| | SSH to the VM | ZMC UI access | ZMC backup server |
| --------------- | ------------- | ------------- | ----------------- |
| **Type** | ssh | Custom TCP | Custom TCP |
| **Protocol** | Not editable | Not editable | Not editable |
| **Port Range** | Not editable | 8008 | 8002 |
| **Source type** | Anywhere | Anywhere | Anywhere |
{% hint style="info" %}
Port 10080 and 10081 must be enabled on the client machine to connect to the Backup server for performing backup and restore.
{% endhint %}
10\. You can then scroll down to the Configure storage category and start specifying the size of your data disk. The recommended size is 100 GB, but you can alter it according to your need. Once you are satisfied, you can launch the instance by clicking on the **Launch instance** button at the bottom right corner of the screen. Once the instance has been successfully launched, the corresponding notification will be displayed at the top of the screen as shown below.
11\. Your newly created VM instance should be visible on the Instances screen. You will need to wait till the two health checks are done, after which you can be assured that your backup server is up and running.
12\. To access the backend, from the Instances screen, click on the **connect** button to connect to your VM via SSH.
13\. Reset the Zmanda Management Console (ZMC) admin user password by running the below command. Please note the password length and complexity requirements. When prompted for a username, enter **admin**
sudo /opt/zmanda/amanda/bin/reset-admin-password
//Requirements
length should be at least 8
Password should have at least one numeral
Password should have at least one uppercase letter
Password should have at least one of the symbols $,@,#,%,^,&,*,~
14\. You will be prompted for the username; please ensure you type it as ‘admin’ and press Enter. The username cannot change as you are setting the admin password here. Next, you will be prompted for the password; type a strong password and press Enter. You will need to re-enter the password to confirm it.
15. You can verify the ZMC services are up and running by the commands **setup-zmc** and **setup-aee** (run as a sudo user). You will notice that the Hashicorp vault service is active but not unsealed
16. Unseal the vault using the below command:
```
sudo setup-zmc unseal
```
17. Go to **network.zmanda.com** and download any patches that are available. Untar them and find and execute the patch executable.
For assistance or questions, please email
18. You can now log in to the ZMC console by opening any browser in your internal network and typing the following in the address bar:
```
https://:8008
```
(The credentials would be the username(admin) and the password you set in steps 12 and step 13)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.zmanda.com/zmanda-classic/installation-and-configuration/step-1-install-zmanda-server/aws-marketplace-installation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.