TF Plan : connection is shut down

[ghost]

This issue was originally opened by @mm-dsiip as hashicorp/terraform#18567. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Terraform Version

0.10.8 and 0.11.7
AWS Module 1.29.0

...

Terraform Configuration Files

resource "aws_lb" "drupal" {
  name = "${data.consul_keys.ck.var.project_name}-${var.install_name}-drupal"
  internal = true
  security_groups = ["${aws_security_group.drupal-alb.id}"]
  tags {
    env = "${var.env}"
    resource-name = "${data.consul_keys.ck.var.project_name}"
    BillingBusinessApp = "${data.consul_keys.ck.var.billing_business_app}"
    Name = "${data.consul_keys.ck.var.project_name}-${var.install_name}-drupal"
  }
  subnets = ["${data.terraform_remote_state.network.aws_subnet_dataapp}"]
}

Crash Output

http://tferdinand.net/PRIVATE/ted/TF_crash_log.txt

Expected Behavior

Plan displays

Actual Behavior

Crash

Steps to Reproduce

1. terraform init
2. terraform apply

[bflad]

Hi @mm-dsiip 👋 Sorry you ran into trouble here.

It appears one of your AWS Application Load Balancer listeners or listener rules is referencing a fixed-response or redirect action, which until #5367 (releasing in version 1.30.0 of the AWS provider, later this week) will unfortunately cause the Terraform crash you are seeing.

To workaround the issue until the new release is out, you can do one of the following:

• Use a custom build of the AWS provider with the above patch
• Use plan/apply resource targeting
• Remove the fixed-response/redirect action from the listener

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!