How to Import an AWS LB SSL Negotiation Policy into Terraform

Import AWS LB SSL Negotiation Policy with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Elastic Load Balancing (Classic) resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live AWS LB SSL Negotiation Policy to managed Terraform.

terraback scan all aws --region us-east-1

terraback aws import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

# aws_lb_ssl_negotiation_policy does NOT support terraform import.
# There is no import block for this resource; define it in HCL and run
# terraform apply against the existing Classic load balancer instead.

Example aws_lb_ssl_negotiation_policy configuration

Here is a realistic AWS LB SSL Negotiation Policy block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "aws_lb_ssl_negotiation_policy" "example" {
  name          = "example-ssl-policy"
  load_balancer = aws_elb.example.id
  lb_port       = 443

  attribute {
    name  = "Protocol-TLSv1.2"
    value = "true"
  }
  attribute {
    name  = "Server-Defined-Cipher-Order"
    value = "true"
  }
}

Gotchas when importing a AWS LB SSL Negotiation Policy

• This resource genuinely cannot be imported: the Terraform AWS provider docs have no Import section for aws_lb_ssl_negotiation_policy, so terraform import will fail. Define it in HCL and apply to adopt it.
• It applies only to the Classic Load Balancer (aws_elb) on a specific lb_port; modern Application and Network Load Balancers use aws_lb_listener security policies instead.
• Because there is no import path, reconcile drift by writing the attribute blocks to match the live policy and running terraform apply, which replaces the policy on that listener port.
• The attribute names (protocols and ciphers) must exactly match an AWS-supported predefined set; an unknown attribute makes the apply fail, so copy them from the live ELB configuration.

Doing it manually with terraform import

The native approach is to write the aws_lb_ssl_negotiation_policy block by hand, then run terraform import aws_lb_ssl_negotiation_policy.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other AWS resources