aws_eip_association.eip_assoc: unexpected EOF (cannot reopen #7910)

[hashibot]

This issue was originally opened by @rainkinz as hashicorp/terraform#9744. It was migrated here as part of the provider split. The original body of the issue is below.

---

Terraform Version

$ terraform -v
Terraform v0.7.7

Affected Resource(s)

aws_eip_association

Terraform Configuration Files

resource "aws_instance" "web" {
  ami = "${var.aws_ami_id}"

  instance_type = "m3.large"

  availability_zone = "us-east-1b"

  key_name = "${var.key_name}"

  iam_instance_profile = "Prod-Webserver"

  # TODO: Change to a VPC
  # vpc_security_group_ids = ["${aws_security_group.main_security_group.id}"]

  security_groups = ["redacted"]

  # The connection block tells our provisioner how to communicate with the 
  # resource (instance)
  connection {
    user = "someuser"

    # The connection will use the local SSH agent for authentication.
    private_key = "${file(var.private_key_path)}"
  }

  tags {
    Name = "web7"
  }

}

resource "aws_eip_association" "web7" {
  public_ip = "54.123.456.789"
  instance_id = "${aws_instance.web.id}"
}

Panic Output

crash.log: https://gist.github.com/rainkinz/8da26dd707c57cc26c71082017acb4f6

Expected Behavior

There should be no error.

Actual Behavior

Terraform crashes

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply

Important Factoids

Running EC2. Trying to associate an existing EIP.

References

I've added the above information to hashicorp/terraform#7910, but cannot reopen, so opened a new bug here.

• tests/resource/aws_lambda_alias: Use Terraform 0.11.12 and later compatible file hashing function #7910

[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!