My problem: Elastic beanstalk environments automatically gets a new elastic IP when created, and it's not possible to force the use of an existing elastic IP when creating a new environment. Even associating an existing beanstalk environment with a different elastic IP than the environment was created with, does not seem to work. (It automatically re-assigns the old elastic IP address again)
An important requirement for the environment is to be able to use A record to point to the environment, and that A record must not be changed if the environment is rebuilt or terminated and then re-created.
In other words, my wish is to maintain an IP for the environment even if I need to re-create it, and preferably not to be forced to use a custom domain.
I'm not finding a way solve this using beanstalk, so the solution will probably be to use cloudformation template instead.
I would really like an good answer from someone with more AWS knowledge than me, to prevent switching to cloudformation without cause :)
Thanks in advance.