We want to attach existing elastic IPs!

[mark-rushakoff]

There's @madhurranjan who opened PR #129 and seems to have implemented the feature. @vkojuharova is asking for this feature in Issue #178. @tonnydourado opened issue #166 about the elastic_ip option not being documented - I banged my head against that for a couple hours trying to figure out why assigning my desired elastic ip to aws.elastic_ip in my Vagrantfile wasn't working.

My project really wants to assign an existing elastic IP to a new Vagrant box too -- we're interested in spending some engineering time for a new pull request if that's what needed. We really don't want to have to install a fork of the vagrant-aws plugin to work side-by-side with other projects using the main implementation.

If sharing some of our engineering time won't help us get this feature onto master, then is there anything else we can do to help?

[benfrye]

+1

[skyshard]

+1

[hyperfocus1338]

+1

[p4w3l]

+1

[njam]

+1

[tomaszdurka]

+2

[unclespeedo]

+1

[jesseangell]

+1

[ttsuchi]

+1

[dawogfather]

+1

[loginx]

👍

[seamusabshere]

+1

[rossmeissl]

+1

[24601]

+1

[cmosguy]

what's the status on this?

[dotmilk]

+1

[darrylb-github]

+1

[ankushnarula]

+1

[joncourt]

+1 please

[seanmcl]

+1 help! :)

[danilogbotelho]

+1

[fletchowns]

Mark's comments sound exactly like the ticket I was about to create. Any chance of this happening @mitchellh ?

[doobiwan]

Yes please! +1

[ghost]

+1

[dkinzer]

+1

[dkinzer]

I'm willing to work on this but since #129 didn't get merged what's the likelihood that anyone's pull request will get merged? It would just be a big waste of time.

[fletchowns]

I emailed @rtyler on Aug 5th asking about the open pull requests on this repo and specifically the elastic ip pulls, but I never got a response.

[frank-u]

+1

[markcwhitfield]

+1

[dbrimley]

I'd like to add my vote for this feature also. When I'm using AWS boxes I want to assign a "known" IP address. This must be a hugely useful feature for a lot of people, as indicated by the comment trail here.

Would anybody please be in a position to comment on this and if it is in the works or likely to be available soon?

The README.md seems misleading on elastic_ip, it states...

elastic_ip - Can be set to 'true', or to an existing Elastic IP address. If true, allocate a new Elastic IP address to the instance. If set to an existing Elastic IP address, assign the address to the instance.

I've tried to explicitly set the ip as suggested...

aws.elastic_ip = "A.B.C.D"

And the logs seem to infer it has been picked up, but the actual elastic IP being allocated is a brand new one.

Launching an instance with the following settings...
-- Elastic IP: A.B.C.D

For reference I'm using what I believe to be the latest released vagrant-aws...

vagrant-aws (0.5.0)

[kmizumar]

+1

[aolchik]

+1

[thiagofigueiro]

+1

[StevenVanAcker]

does elastic_ip work? I allocated an elastic IP on AWS and then told vagrant about it, but it seems to ignore the setting. I'm using vagrant-aws 0.7.0

[sameronline]

+1