Talk Maintenance

Got a bunch of Summary emails. (not complaining) Looks like its working!

Screenshot_20180606-153248_Samsung Internet

Something is working again, and I’ve received some email notifications as well so, yay y’all did it? Maybe?

Turns out the IP address somehow changed

That’s the very nature of AWS when VMs get turned off. We now have a script that would auto update cloudflare when/if there is a change. So if we’re able to have them verify via DKIM and/or host name then great if not… well that means we need to setup some Elastic IPs and Loadballencers which that gets massively costly on their own.

That is not the nature of EC2, with EC2 you have Elastic IPs and Network Interfaces. Either of those resources can be assigned to any EC2 instance. If you destory an instance or swap to a new one, you can easily move the Elastic IP or Network Interface.

EC2 does not autogenerate new ip addresses when VMs get turned off.

To Quote AWS themselves[¹]:

When you stop/start your instance, the IP address will change. Unfortunately there is no way to avoid this scenario in EC2. If you reboot the instance (within the Operating System, or via the console), it will keep the same IP addresses. Unfortunately it is not possible for us to reassign the address to your instance as that address would have been released back into the pool used by other EC2 instances.

If you want to avoid this issue in future, depending on your needs:
If you only need a fixed public IP address, you can assign an Elastic IP address to your instance. Further information on Elastic IP addresses is available from here.
If you need both public and private IP addresses to remain the same throughout the lifetime of the instance, you can launch your instance in VPC instead. The private IP address assigned to an instance in VPC remains with the instance through to termination.

Thus the states of an IP can be:

  • Reboot instance: keeps IP Address
  • Stop then Start instance: new IP Address on startup
  • Shutdown instance: loses IP Address
  • Terminate instance: loses IP Address

Therefore anything operation that makes the VM go into ACPI state S4, S5, S6 will drop the address, anything like S0, S1, or S3 would keep the address.

That is outdated inaccurate information from before EC2 used their VPC configuration.

ok, so how did the IP address change when the vm was turned off?

You’re right, that would definitely be why. Great catch. I was very confused :slight_smile:

We should plan another migration to move them to Elastic IP’s.

@Draco why was this moved to Members Only?

Because we are talking about internal addresses and server names and the public IMO does not need to be privy to it … we could split it into a private convo rather than move the whole thread… it was just getting rather member only type

3 Likes

We’re out of the trenches, Talk notifications should be 100% back in order, you should receive them immediately after they’re sent.

The missing images I think are just… gone. Sorry.

4 Likes

I’d say more like /c/Infrastructure instead.

Would you say these things are resolved? It seems to be acting normally (at least to me, without looking at any logs or anything) …

I marked it as resolved here: https://talk.dallasmakerspace.org/t/talk-maintenance/37390/32?u=lukestrickland

2 Likes

Closed in helpdesk: closed by denzuko on 2018-06-07