You can upgrade the DR AWS proxy environment to the latest versions from the Management Console with a single click.
📝 Note:
CentOS has reached end-of-support. If you have your proxy deployed on CentOS(AWS proxy version 6.3.3 or earlier), you must manually upgrade it to Ubuntu proxy by deploying the CloudFormation stack. For more information, see Deploying CloudFormation stack template for migrating AWS Proxy from CentOS to Ubuntu.
What is an AWS proxy environment
An AWS proxy environment is the infrastructure that Druva needs to communicate securely with your AWS account and run disaster recovery (DR) workflows.
Think of it as a dedicated workspace within your account that includes:
Networking: VPC Endpoints, Network Interfaces (ENIs), Route Tables, and Route 53 zones.
Compute: The EC2 instances used for the DR proxy.
Security: IAM roles and Security Groups that allow the proxy to manage resources during a recovery.
Versions and maintenance
Druva monitors this environment’s version to ensure it remains up to date. Version statuses include:
Already on the latest version
Upgradable to the latest version
Not upgradable
For more details on these statuses, see the procedure.
Checking your AWS proxy environment status early helps you catch and fix issues before they become a problem during a recovery.
❗ Important
An environment is strictly tied to a specific AWS Account + Region + VPC combination. If you move to a new VPC, Region, or Account, you cannot move or share the existing environment. You must set up a new one for that specific location.
Key considerations
Redeployment of older proxies, version 6.x, via Cloud Formation template:
In case of redeployment of proxy version 6.x, the AWS infrastructure is upgraded and a new AWS proxy instance, version 7.x, is activated.
After the new proxy is active and running, Cloud Formation template terminates the older proxy from AWS. It will be shown as disconnected and you need to delete it from the management console.
Procedure
Log in to the Management Console.
On the menu bar, click All Organizations, and select the required organization from the drop-down list.
On the menu bar, click Disaster Recovery.
In the left pane, select the Phoenix AWS Proxies tab.
In the Environment column, you can view the current status of each Druva AWS proxy along with its version number.
Latest version: The environment is already on the latest supported version.
Example: You recently deployed or upgraded the proxy using the latest CloudFormation template. In this case, no action is needed. You can continue to run DR restores, failovers, and failbacks.
Upgradable: The environment is on an older version, but can be updated.
Example: You deployed the proxy a few months ago, and new environment enhancements (new endpoints, IAM, etc.) are available. In this case, click Upgrade > Upgrade Environment, and then deploy the CloudFormation stack in your AWS account.
📝 Note
You must select proxies from a single AWS account and region for the environment upgrade.
Non upgradable: The environment is too old to update.
Example: Your proxy environment was created with an older environment template. In this case, deploy a new AWS proxy using the latest CloudFormation template, and then delete the old proxy.
In progress: A CloudFormation stack for this environment is currently being created or updated. Wait for it to complete.
📝 Note
Jobs that are in progress at the time of upgrade will resume after the upgrade is complete.
Example: You have just launched a CloudFormation stack from the Upgrade Environment screen. In this case, wait until the stack completes. Running jobs will resume after the upgrade completes.Unknown: Druva does not have enough information to determine the status of the AWS Proxy environment.
Example: Old proxies may show Unknown status until they are upgraded. In such cases, the AWS proxy will appear as Upgradable. Upgrading the AWS Proxy to version 7.0.2 or later allows the proxy to correctly detect and report the environment status that is displayed on the UI.
Select the proxy for which you want to upgrade the environment and click Upgrade. Select Upgrade Environment from the dropdown menu.
Click Yes, Proceed on the confirmation dialog box.
After you confirm, you will need to select the Create CloudFormation Stack option on the Upgrade AWS Proxy Environment screen. You will be redirected to the AWS console.
On the AWS console, the required fields are auto-populated.
The stack deployment will complete within 15 minutes. Once the stack is successfully deployed, you can see the newly deployed proxy on the Phoenix AWS Proxies page.
FAQs
My proxy is up to date. Why do I still need to upgrade the environment?
My proxy is up to date. Why do I still need to upgrade the environment?
Proxy upgrade only updates the software running on the proxy instance. Many DR enhancements also require new or updated AWS resources, for example, additional VPC endpoints, new IAM permissions, or updated DNS entries.
If the environment is not upgraded:
New DR features may not work as expected.
DR workflows (restore, failover, failback) can fail due to missing or outdated AWS resources, even though the proxy agent is on the latest version.
Upgrading the environment keeps the infrastructure in sync with the proxy.
When should I upgrade the environment, and when should I deploy a new proxy?
When should I upgrade the environment, and when should I deploy a new proxy?
If the Environment status is Upgradable:
Use the Upgrade Environment option. This triggers a CloudFormation stack that updates the existing environment in place to the latest supported version.
If the Environment status is Not upgradable:
The current environment version is too old to be updated in place. You must deploy a new DR AWS proxy using the latest CloudFormation template. This creates or updates the environment to the latest version for that account, region, and VPC.
What should I do if the environment status shows “Unknown”?
What should I do if the environment status shows “Unknown”?
“Unknown” means Druva does not yet have enough information to calculate the environment version. This typically happens for proxies that were created before environment tracking was introduced.
To resolve it:
Upgrade the proxy agent to a version that reports environment details, or
Deploy a new DR AWS proxy using the latest CloudFormation template.
Once the environment details are registered, the Environment column will show a status such as Latest version, Upgradable, or Not upgradable.