Terraform for HP-UX Legacy Workloads: Migration Patterns

HP-UX entered end-of-support for new releases years ago. In 2026 the only credible Terraform pattern is migration: provisioning the target Linux estate, building a connectivity bridge, and porting workloads. Direct HP-UX provisioning by Terraform doesn't exist — HPE Synergy / OneView handle the iron.

What Terraform Owns

Lift-and-Shift Target on AWS

resource "aws_instance" "rhel_replace" {
  ami           = data.aws_ami.rhel9.id
  instance_type = "m7i.4xlarge"
  subnet_id     = var.private_subnet_id
  iam_instance_profile = aws_iam_instance_profile.app.name
 
  root_block_device {
    volume_size = 200
    volume_type = "gp3"
    encrypted   = true
  }
 
  tags = {
    Name        = "hpux-replacement-app1"
    Migration   = "from-hpux"
    Application = "billing"
  }
}

Direct Connect to the HP-UX Site

resource "aws_dx_gateway" "corp" {
  name            = "hpux-bridge"
  amazon_side_asn = 64512
}

Best Practices

• Don't try to "Terraform HP-UX" — its lifecycle is HPE OneView / Ignite-UX.
• Track every dependency during migration with tags (Migration=from-hpux, Application=...).
• Pre-build observability on the new Linux side (CloudWatch / Grafana) before cutover.
• Use AWS MGN or Azure Migrate for application replatforming where source code is unavailable.

Related

• Terraform for AIX on Power
• Terraform for Oracle Solaris Legacy