View a markdown version of this page

Key considerations for EC2 launch templates - AWS Elastic Disaster Recovery

Key considerations for EC2 launch templates

Review the following key rules and interactions before you modify an EC2 launch template for use with AWS Elastic Disaster Recovery.

  1. Instance type – AWS Elastic Disaster Recovery uses the instance type set on the launch template unless Instance type right-sizing is activated. If right-sizing is active, it overrides the launch template value.

  2. Subnet – If you do not have a default VPC, you must explicitly define the subnet. Failure to do so results in errors when launching drill or recovery instances.

  3. Private IP and subnet – If you use the Copy private IP feature, ensure that the IP is included in the subnet's CIDR block range. Otherwise, instance launch fails.

  4. Network interfaces – AWS Elastic Disaster Recovery manages the primary network interface (device index 0). Additional network interfaces defined in the launch template are preserved and passed through at launch time.

  5. Custom device name – Do not alter this field. AWS Elastic Disaster Recovery uses the device name as defined on the source server to map disks on the drill or recovery instance.

  6. Disks – You cannot add disks to the EC2 launch template. Any disks added that do not exist on the source server are ignored.

  7. Launch template name – Do not alter this field. AWS Elastic Disaster Recovery automatically generates this name.

  8. Volumes – For each EBS volume, AWS Elastic Disaster Recovery uses the user-selected values. If no matching volume exists in the launch template, AWS Elastic Disaster Recovery uses default values. If the launch template includes a volume that does not exist on the source server, the system disregards it. If you delete the EC2 launch template, the service creates a new one with default values.

  9. KMS key – Encryption for recovery volumes is controlled through the EBS Encryption section of the replication settings within the AWS Elastic Disaster Recovery console. The launch template's KMS key field is not used by AWS Elastic Disaster Recovery during volume creation. To encrypt recovery volumes with a specific KMS key, configure it in the replication settings.

  10. Automatic cleanup – AWS Elastic Disaster Recovery deletes the EC2 launch template for source servers that have been disconnected from AWS Elastic Disaster Recovery or for which recovery has been finalized.

  11. Tags – Launch template tags always take precedence over tags set in the AWS Elastic Disaster Recovery console or tags manually added to the server.