Skip to main content
Druva Documentation

Deploy Phoenix AWS proxy

Phoenix Editions: File:/cross.pngBusiness         File:/tick.png Enterprise     File:/tick.pngElite
(Purchase Separately)

This topic provides instructions for deploying the Phoenix AWS proxy using AWS CloudFormation. AWS CloudFormation automates the deployment process of creating and managing the AWS resources in the AWS environment. It also facilitates the registration and activation of the Phoenix AWS Proxy with the Phoenix Cloud.

To register and activate a Phoenix AWS proxy, you must first select an AWS region on the Phoenix Management Console and create an AWS CloudFormation Stack on the AWS Management Console.

Before you begin

You must register the Phoenix AWS proxy in the same region as the server storage region.


To register a Phoenix AWS proxy, perform the following steps:

Step 1: Select an AWS region on the Phoenix Management Console 

  1. Log in to the Phoenix Management Console.
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Disaster Recovery.
  4. In the left pane, click the Phoenix AWS Proxies tab.
  5. On the Phoenix AWS Proxies page, click Register Phoenix AWS Proxy.
  6. On the Register Phoenix AWS Proxy page, from the AWS Region drop-down list, select the AWS region where you want to deploy the proxy. For example, us-west-2.

    NoteDeploy the Phoenix AWS proxy in the same region where the virtual machines that you intend to configure for disaster recovery are backed up in Phoenix. For example, if the virtual machines are backed up to a storage in Phoenix that is located in the US-East region, deploy the Phoenix AWS proxy in the US-East region.


    The Activation Token section displays an activation token that is used while creating the CloudFormation Stack.

    Note: Phoenix lists the activation token under Manage > Activation Tokens.

  1. In the AWS CloudFormation Stack section, click Create CloudFormation Stack to register the Phoenix AWS proxy.

If you are logged in to the AWS Management Console, you are directed to the Quick Create Stack page. Else, you are directed to the login page of the AWS Management Console. Use your credentials to log in and the Quick Create Stack page appears.

Step 2: Create a CloudFormation Stack on the AWS Management Console

The Quick create stack page on the AWS Management Console uses a proxy deployment template depending on your first-time proxy deployment or the subsequent deployments. This page enables you to configure parameters for your AWS resources defined in the template.

The Quick create stack page populates values in the following fields:

  • Template URL: Displays the URL of the Druva deployment template used for your proxy deployment.
  • Stack description: The description of the Druva deployment template used.
  • Stack name: Displays the name generated by Phoenix for your stack.
  • DeploymentType: Displays the Druva deployment template type selected for the proxy deployment:
    • InfraAndProxyDeployment: This template is used for the first-time proxy deployment. It is a JSON-based CloudFormation template, which is used to deploy the IAM policies, roles, and proxy instances in your AWS account.

      Note: If you have deployed an IAM role using the InfraProxyDeployment option and try to use the same option to launch an instance, the stack creation process fails as it tries to create the DruvaIAMRole role, which is already created.

    • ProxyDeployment: This template is used to deploy only proxy instances and reuse the existing IAM policies and roles created for your AWS account during the previous deployments.
  • PhoenixActivationToken: Displays the Phoenix activation token generated based on the selected AWS storage region on the Phoenix Management Console.

Provide the Phoenix Configuration, Network Configuration, and Amazon EC2 Configuration parameters for your AWS resources/EC2 instances.



  1. InstanceCount: Specify the number of proxy instances that you want to launch. You can specify up to 5 instances. The default value is 1.
  2. VPC: Select a Virtual Private Cloud (VPC) network specific to the AWS account to launch the Phoenix AWS proxies.
  3. Subnet: Select a subnet to launch the Phoenix AWS proxies in the specific network in your VPC.
  4. InstanceType: Select the instance type for the Phoenix AWS proxy.

    Note: It is recommended to select the instances based on the following configuration: 8 CPUs, 16 GB memory, 3500 Mbps bandwidth, 10,000 IOPS.

  5. KeyPair: Select an EC2 key-pair to enable SSH access to the proxy instance.
  6. AutoAssignPublicIP: Select the option based on the chosen subnet.
    • true: Select this option if you want to assign a public IP after launching the Phoenix AWS proxy and have chosen a public subnet in Step 3.
    • false: Select this option if you do not want to assign a public IP after launching the Phoenix AWS proxy and have chosen a private subnet in Step 3.
      The stack template may list certain capabilities for AWS CloudFormation to create the AWS resources in your stack.

      Note: When you deploy Phoenix AWS proxy using the CloudFormation Stack, Phoenix DRaaS opens an outbound port 443 (HTTPS). For secured remote login, you can open an inbound port 22 (SSH). 

  7. In the Capabilities section, select the acknowledgment check boxes and click Create stack.

After you click Create stack, Amazon creates the stack with the configuration parameters you set on the Quick create stack page. Verify the status of stack creation on the Stacks page on the AWS Management Console.

  • If the status is CREATE_COMPLETE,  Phoenix lists the registered Phoenix AWS proxy on the Phoenix AWS Proxies tab on the Phoenix Management Console.
  • If the status is CREATE_FAILED, check the Events section on the Stacks page on the AWS Management Console for more details. You can also contact Druva Support. See Troubleshoot common scenarios.
    You can view the deployed AWS resources, such as EC2 instance IDs and security groups, on the Resources tab on the Stacks page.

After the registration completes successfully, the Phoenix AWS proxy appears on the Phoenix AWS Proxies page. 


Note: When you delete a stack, AWS does not delete resources attached to the stack. Ensure that you manually delete the resources attached to the AWS account.

  • Was this article helpful?