1. Shut down the old ePO Application Server and Local Agent Handler.
2. Log on to the AWS console and perform the following steps if your old ePO Application Server and Local Agent Handler are running:
   1. Shut down or stop the ePO Application Server instance from the EC2 instances.
   2. Navigate to the Load Balancing, Target Groups, and remove the old ePO Application Server from the Targets.
   3. Navigate to Load Balancers, and select Agent Handler Load balancer, then remove the Local Agent Handler of ePO.

Set up the new ePO Application server:

IMPORTANT: You must be aware of your existing ePO server configuration before you continue with the following steps.

1. Create a new Amazon EC2 instance on the same AWS region for the new ePO Application server. This instance must be based on the AMI Name Windows_Server-2016-English-Full-Base-2018.07.11, which is used for the ePO server.
2. Select the EC2 instance type, which is the same as your old ePO Server Application Server configuration. For example, m5.Large
3. Assign the existing VPC of your ePO Application server and select the same Private Subnet. For example: vpc-xxxxx, PrivateSubnet1 (10.0.2.x)
4. Select the Storage for the server and add Tags (The same as your old ePO server).
5. Assign the existing Security Groups. For example: Assign RDPAdminSecurityGroup, ePOInstanceSecurityGroup, and ePOLoadBalancerSecurityGroup.
6. Select the AWS Key Pair.
7. Wait for the EC2 instance to start successfully.

Install and configure the new ePO Application Server:

1. Log on to the new ePO Application Server EC2 instance and copy the ePO installer.
2. Reinstall the ePO software through the installer. Make sure to point to the existing RDS instance with the option Restore from existing Snapshot.
3. Enter the AWS RDS details, RDS Endpoint URL, Database name, and Password.
   
   NOTE: You can obtain the RDS details from the AWS RDS instance page.
    
4. Provide the ePO Administrator credentials of your old ePO server and Disaster Recover Passphrase.
5. Wait for the installation to complete.
6. Add the new ePO Application Server to the Load Balancers, Target Groups. Targets must be reporting as Healthy.
7. Add the new Local Agent Handler to the Agent Handler Load balancer from Load Balancers, Instances. The status must show InService.
8. Attempt to log on to the ePO console.
   
   NOTE: If you are unable to log on, review all steps performed in this article and make sure that they have been properly completed. If you can't resolve the console logon issue, contact Technical Support for further assistance before proceeding. See the Related Information section for contact details.

NOTE: Some of the configurations performed earlier as part of the CloudFormation Template deployment might not be available after the Disaster Recovery procedure. For example: CloudWatch Logs and Metrics for the new ePO Application Server