Skip to main content
Druva Documentation

Launch Phoenix AWS Proxy

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

Phoenix AWS Proxy orchestrates the process of AMI creation on the defined schedules.

Before you begin

Before you launch the Phoenix AWS Proxy, ensure the following:

  • You have an AWS account with valid login credentials.
  • You have root permission to create and apply IAM roles.
  • You have an AMI ID. For more information, see Get AMI ID.  Phoenix supports the following regions for disaster recovery:
    • AWS GovCloud
    • US East (N. Virginia)
    • US West (N. California)
    • US West (Oregon)
    • EU (Ireland)
    • EU (Frankfurt)
    • Asia Pacific (Mumbai)
    • Asia Pacific (Tokyo)
    • Asia Pacific (Singapore)
    • Asia Pacific (Sydney)
    • South America  (Sao Paulo)
    • Canada (Central)
    • EU (London)
  • You do not proceed with the AMI IDs for the following AWS regions because Phoenix does not support the following regions for disaster recovery:
    • Asia Pacific (Seoul) 
    • China (Beijing) 
    • US East (Ohio)
  • You do not launch Phoenix AWS Proxy in the Sao Paulo region using the EBS volume type.
  • When you deploy a new Phoenix AWS Proxy with version 4.8.0 or later in your AWS account, Phoenix creates DR copies of the virtrual machine backup data instead of the AMIs in your AWS account.
  • Phoenix does not support auto-upgrade of the Phoenix AWS Proxy from version 4.7.6 to 4.8.0. You must deploy the new Phoenix AWS Proxy in your environment.

To launch Phoenix AWS Proxy

  1. Log in to the AWS account. 
  2. On the top-right corner, select the AWS region where you want to deploy the Phoenix AWS Proxy.

    NoteLaunch 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.

  3. On the menu bar, click Services
  4. Under the Compute section, click EC2.
  5. In the left pane, click Images AMIs.
  6. From the Owned by me drop-down list, select Public images.
  7. Copy and paste the AMI ID into the search box and click the search icon.
    For more information about AMI ID, see Get AMI ID.
  8. Select the searched AMI ID, and click Launch.
  9. On the Choose and Instance Type page, select one of the following instance types:
    • Mainline Cloud: c5.2xlarge
    • Gov Cloud: c5.2xlarge
  10. Click Next: Configure Instance Details.
  11. On the Configure Instance Details page, do the following:
    • Number of instance: Enter the number of the instances corresponding to the number of Phoenix AWS Proxies. By default, Phoenix sets the instance to 1.
    • Network: Select the required network from the drop-down list or create a new VPC.
      • To create a VPC, perform the following steps:
        1. Click the Create new VPC link.
        2. On the VPC Dashboard, click Create VPC.
        3. On the Create VPC page, provide the VPC name, the IP address range for the VPC in the CIDR block format, and the tenancy option.
        4. Click Yes, Create.
    • Subnet: Select the required subnet from the drop-down list or create a new subnet.
      • To create a subnet, perform the following steps:
        1. Click the Create new subnet link.
        2. On the VPC Dashboard, click Create Subnet.
        3. On the Create Subnet page, provide details such as the subnet name, the VPC for the subnet, the availability zone where subnet will reside, and the CIDR block format.
        4. Click Yes, Create.
    • IAM role: Select the required IAM role from the drop-down list to attach to the Phoenix AWS Proxy or create a new IAM Role.

    Note: Ensure that the IAM role uses the latest IAM policy downloaded from the Phoenix Management Console.

    You can set the other options on the Configure Instance Details page as per your preference.

  12. Click Next: Add Storage.
  13. On the Add Storage page, set the size of the volume type as per your requirement. By default, Phoenix sets the size to 32 GB.

    Note: The set size for the volume type should not be less than 32 GB.

  14. Click Next: Add Tags.
  15. On the Add Tags page, enter a name for the tag in the key-value format.
  16. Click Next: Configure Security Group and do one of the following to configure security group:
    • Create a new security group. Provide the following details.
      • Security group name: A unique security name for the group.
      • Description: A description of the added security group.
      • Rules: Create a security group with the following details for Phoenix AWS Proxy.
        • Type: SSH
        • Ports: 22
        • Protocol: TCP
        • Source:
          By default, AWS provides the range of IPs, which implies that this security group allows incoming SSH requests from any machines. If you select the default IP range for the Source field, AWS displays a warning message as shown in the following screenshot:

          To limit the access to the EC2 instance from any IP address, you can modify the IP range based on the security requirements.
      • Add rule: Port 443 for communication with Phoenix Cloud
    • Select an existing security group.
  17. Click Review and Launch.
  18. On the Review Instance Launch page, verify all the information and click Launch.
    The Select an existing key pair or create a new key pair page opens.
  19. Select the Create a new key pair option from the drop-down list.
  20. Provide a unique key pair name and click Download Key Pair
    This downloads the <unique key pair name>.pem file on the machine.
    Ensure that you save the downloaded private key (.pem) file for further use. The .pem file is required while logging into the instance. If you do not have the .pem file, you cannot log in to the instance.
  21. Click Launch Instances. The Launch Status page notifies the launch of your instance. You can click View launch log to view the launch initiation details. Default username of the Phoenix AWS Proxy is centos.

Ensure that the Phoenix AWS Proxy runs as an instance in your AWS environment. 

  • Was this article helpful?