Common errors while launching drill/recovery/test instance due to misconfiguration in launch template in MGN/DRS.

Error 1: InvalidParameterCombination - Network Interface Configuration

Error Message

An error occurred (InvalidParameterCombination) when calling the RunInstances operation: A network interface may not specify both a network interface ID and a subnet

Cause

• When configuring a launch template, you cannot specify both a subnet and an Elastic Network Interface (ENI) simultaneously. This is because the subnet is automatically determined by the ENI configuration. You must choose either:

  • Specify a subnet, OR
  • Specify an ENI"

• Auto-assign public IP' option and Delete on termination option are set to 'Don't include in launch template'

Resolution

1. Navigate to source server in MGN/DRS console → Launch settings → EC2 launch template → Edit
2. Choose either subnet OR ENI configuration (not both)
3. Set "Auto-assign public IP" and "Delete on termination" to "Don't include in launch template"
4. Set the new template version as default:
   • Go to EC2 console → Launch Templates
   • Select your template
   • Actions → Set default version
   • Choose latest version → Set as default

Error 2: VPCIdNotSpecified - Default VPC Issue

Error Message

An error occurred (VPCIdNotSpecified) when calling the RunInstances operation: No default VPC for this user. GroupName is only supported for EC2-Classic and default VPC.

Cause

• No default VPC available
• Incorrect/missing subnet specification
• Launch template version with correct settings not set as default

Resolution

1. Specify a valid subnet in the launch template
2. Ensure the subnet exists and is correctly configured
3. Set the updated template version as default

Error 3: InvalidParameterValue - IP Address Range

Error Message

An error occurred (InvalidParameterValue) when calling the RunInstances operation: Address "IP Address" does not fall within the subnet's address range

Resolution

For Enabled "Copy Private IP" Option:

1. Check if "Copy Private IP" is set to "Yes" in DRS launch settings
2. If enabled:
   • Navigate to EC2 launch template
   • Click "Edit"
   • Go to "Advanced network configuration"
   • Verify that the primary IP address is within the specified subnet's CIDR range

For Disabled "Copy Private IP" Option:

• If previously enabled and later disabled:
  • Manually remove the IP address from the launch template
  • Important: Simply disabling the "Copy Private IP" option is insufficient
  • The IP address needs to be explicitly deleted from the launch template settings

Error 4: InvalidParameterValue - Reserved IP Address

Error Message

An error occurred (InvalidParameterValue) when calling the RunInstances operation: Address "IP Address" is in subnet's reserved address range

This error usually occurs when mentioned IP address in lunch template is already reserved by AWS. The first four IP addresses and the last IP address in each subnet CIDR block are not available for your use, and they cannot be assigned to a resource, such as an EC2 instance. For example, in a subnet with CIDR block 10.0.0.0/24, the following five IP addresses are reserved:

• 10.0.0.0: Network address
• 10.0.0.1: Reserved by AWS for the VPC router
• 10.0.0.2: Reserved by AWS for DNS server
• 10.0.0.3: Reserved by AWS for future use
• 10.0.0.255: Network broadcast address

Error 5: InvalidGroup.NotFound - Security Group Issue

Error Message

An error occurred (InvalidGroup.NotFound) when calling the RunInstances operation: The security group 'sg-' does not exist in VPC

Resolution

Edit the launch template and select a valid security group that exists within the chosen VPC.

Error 6: VcpuLimitExceeded - Instance Capacity

Error Message

An error occurred (VcpuLimitExceeded) when calling the StartInstances operation: You have requested more vCPU capacity than your current vCPU limit of 16 allows for the instance bucket that the specified instance type belongs to.

Resolution

1. Visit the AWS Service Quotas Console
2. Navigate to the EC2 service section
3. Locate the specific instance family vCPU quota
4. Submit a quota increase request to AWS Support

Note: AWS typically reviews and processes quota increase requests within 24-48 hours, depending on the requested limit and your account history.

For more information about requesting vCPU limit increases, see How do I request a vCPU limit increase for Amazon EC2 instances?