Bring-Your-Own EIP

[OkJaybird]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request.

Tell us about your request When requesting a public IP attached to an instance, a new EIP is always created (or the environment creation fails due to max EIP usage reached). It would be useful to be able to optionally specify a pre-existing EIP. This way the EIP could be reserved / managed separately, and the EIP would still be retained in the event the EB environment is destroyed.

Is this request specific to an Elastic Beanstalk platform? If so, which one(s)? All

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I want to run a public service that cannot be placed behind a load balancer and thus must be run as a single-instance. Consumers connecting to the service need a reliable IP to access it, but if I ever want to move the service out of EB and run it elsewhere, I'll lose the attached EIP. If I could define an EIP separately and tell EB to use it, I would have a separately managed EIP I can share with clients confidently.

Are you currently working around this issue? No, we cannot use EB to run the service.

Additional context N/A

Attachments N/A

[Sekhar-Kutikuppala]

Hi @OkJaybird Can you tell us more about your use case and why your application cannot be placed behind a ELB?

[jordanade]

I would like to be able to not have to use a load balancer and assign EIPs to individual members of a scaling group and have to them auto-reassigned to new machines as necessary. There's just some situations where you can't use a CNAME.

[ggedde]

Same, although I am just looking when setting up a "Single-instance environment" there should be an option to select an EIP.

• Also when removing or terminating the environment the EIP should NOT get released. Currently it does. Same for Re-Building the Environment. It should just use the same EIP that you selected.

I am looking into using the .platform hooks to see if there is a workaround for now, but so far unsuccessful.

[ggedde]

I was able to add a script with aws ec2 associate-address --allocation-id eipalloc-xxxxxxxxx --instance-id $(cat /var/lib/cloud/data/instance-id) with another EIP on a single instance deployment. The script does run successfully. However, moments later EB reassigns the old (unwanted) EIP to the instance. So there is some configuration somewhere running on health checks to reassign the EIP, but I cannot find any way to edit this. So it seems there is no way to currently Re-assign the EIP to a EB Configuration.

If someone found a way then please let me know. Thanks