stable IPs across reboots and redeploys for AWS

[Loïc Gomez]

Hi,

When an AWS instance gets rebooted or is redeployed, it sometimes gets affected a new IP address.
We need to be able to have a stable IP address on AWS instances.

Let us know if we can help in any way!

Thank you

[Harry Pidcock (hpidcock)]

Note for juju team: This feels like the network modelling could allow for allocation and attachment of elastic IPs. In the same way we deal with storage.

[Benjamin Allot (ballot)]

Another occurrence of this today.

We had a single controller unit which rebooted and got a new external IP address on GCP.

As a result, all the agent.conf of all units had to be manually updated to match the new IP, using a shell loop with `juju ssh`.

The internal IP couldn't be used despite being unchanged, because it's not in the same VPC (see https://cloud.google.com/compute/docs/ip-addresses).

Seen on juju version 2.9.22.

[Juan M. Tirado (tiradojm)]

Could we confirm this issue still happens on more recent versions 2.9.37 or 3.1-beta1?

[Haw Loeung (hloeung)]

Yeah, it would unless Juju has added support for assigning floating IPs in AWS (and other public clouds)? That's https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html