Public IP Never Assigned When Requested in VPC

[dan9186]

When trying to create a new AWS Instance within a VPC, a public IP is never assigned though requested.

variable "access_key" {}
variable "secret_key" {}

provider "aws" {
    access_key = "${var.access_key}"
    secret_key = "${var.secret_key}"
    region = "us-east-1"
}

resource "aws_instance" "example" {
        ami = "ami-76817c1e"
        instance_type = "t2.micro"
        key_name = "devkey.pem"
        subnet_id = "subnet-1234abcd"
        security_groups = ["sg-1234abcd"]
        associate_public_ip_address = true
}

[pearkes]

Thanks, tagged as a bug!

[dan9186]

Well I tried further to confirm that it was my issue, and turns out it was. I thought I was using the latest release, but wasn't. I've updated, and the problem was resolved.

[mitchellh]

Great to hear! Closing

[seanherron]

@dan9186 I'm experiencing this same issue. Running Terraform v0.2.0.dev (b8b012633c3ed8611d2f58d0ae277da8ea472400). Am I missing something?

[dan9186]

What does the output of your terraform plan look like?

You should see something similar to this

+ aws_instance.example
  ami:                         "" => "ami-76817c1e"
  associate_public_ip_address: "" => "1"
  availability_zone:           "" => "<computed>"
  instance_type:               "" => "t2.micro"
  key_name:                    "" => "dev.pem"
  private_dns:                 "" => "<computed>"
  private_ip:                  "" => "<computed>"
  public_dns:                  "" => "<computed>"
  public_ip:                   "" => "<computed>"
  security_groups.#:           "0" => "1"
  security_groups.0:           "" => "security_groups"
  subnet_id:                   "" => "subnet-154da974"

[seanherron]

+ aws_instance.test
    ami:                         "" => "ami-a0ff23c8"
    associate_public_ip_address: "" => "1"
    availability_zone:           "" => "<computed>"
    instance_type:               "" => "t2.medium"
    key_name:                    "" => "dev.pem"
    private_dns:                 "" => "<computed>"
    private_ip:                  "" => "<computed>"
    public_dns:                  "" => "<computed>"
    public_ip:                   "" => "<computed>"
    security_groups.#:           "0" => "1"
    security_groups.0:           "" => "sg-number"
    subnet_id:                   "" => "subnet-number"

However, the instance is not associated with a public IP unless I add an Elastic IP to it.

[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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.