Article number
Affected Versions
Source Hypervisor
Target Hypervisor

Error: “Address is in use” and VPG in Error Status After Recovery to AWS

Viewed 396 times


An administrator may experience a Recovery to AWS task failure and the VPG falling into Error status.

Root Cause

Prior to kicking off said Failover, a Private IP was assigned to a VM to spin up with on the AWS site.

The Failover fails due to the configured Private IP already being assigned to another EC2 instance in the same network.


A Failover reportedly fails to AWS and a VPG enters an "Error" status.

The ZVM logs will report the following failure returned by AWS:

,AWSImage,LaunchInstanceFromAmi,Failed to create instance type <Instance_Type> in AZ <Availability_Zone>: Address <IP Address> is in use.,"Amazon.EC2.AmazonEC2Exception Boolean HandleException(Amazon.Runtime.IExecutionContext, Amazon.Runtime.Internal.HttpErrorResponseException) Amazon.EC2.AmazonEC2Exception: Address <IP Address> is in use. ---> Amazon.Runtime.Internal.HttpErrorResponseException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.


To workaround this issue, follow the steps below:

  1. If the VPG is in the "Error" status, you will need to recreate the VPG manually (which may require a Force Delete).

    1. Note: At this time, preseed is not supported into AWS, thus an initial sync will be seen.

  2. Prior to next attempt, either remove the Private IP address entirely from the VPG Configuration or pick a Private IP address that is not in use within the VPC in AWS and try again.