---
alias: user-guide-automation-manager-deploy
tags:
- connect iot
description: "Deploy Automation Manager facilitates the deployment of an existing Automation Manager instance"
---

# Deploy Automation Manager

:lock: AutomationManager.**Deploy**

## Overview

This operation is used to deploy an existing **Automation Manager**.  

## Setup

No specific setup is required other than to meet the preconditions of the transaction.

!!! note
    If the Automation Manager requires storage resources, such as Persistent Volumes (PVs), they must be configured in advance, according to [[user-guide-automation-manager-configure|Configure Automation Manager Deployment]]. Otherwise, they won't be created automatically. If this happens, you’ll need to undeploy, update the configuration, and deploy again — which may cause issues if existing Persistent Volume Claims (PVCs) can’t be released due to permission restrictions.

## Preconditions

* The **Automation Manager** exists in the system.
* The **Automation Manager** has the Deployment Mode set as AutomaticDeploy.
* The **Automation Manager** has the Deployment State different from Ready.

## Sequence of Steps

1. Select **Deploy** to perform the operation. The current Deployment State will be changed to Ready.

## Dependency

This requires the installation of the `Automation Manager Controller`. This component will continuously query for new managers that are in a ready state, or Managers that were in a ready state but were undeployed. When the components receives differences it will deploy or undeploy new Manager instances.