Fair point. I suppose it is then just a risk that someone can choose to accept; in practice it probably won't change, but Amazon makes no guarantees that it will be the same. :-)
On Mon, Dec 30, 2013 at 3:12 PM, Greg Andrews <[email protected]> wrote: > > Peter Gehres wrote: > >> "For instances launched in EC2-Classic, a private IP address is >> associated with the instance until it is stopped or terminated." >> > > > Notice "stopped" and "terminated" are listed, but "rebooted" is not. I > have rebooted EC2-Classic instances and not lost the private/public > addresses. The main thing is a normal reboot rather than having the > instance down for a longer period of time. > > The one time I experimented with this (on instances in Tokyo), I had to > leave the instance stopped for 20-30 minutes before its addresses changed. > IMO, it's overstating the case to say a simple reboot (down for only > seconds) will force a new private/public address on an instance. > > -Greg > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Peter Gehres Site Reliability Engineer | AppDynamics, Inc. www.appdynamics.com | AS62897 -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
