Why it isn’t re-assigned a public IP address and public IP DNS for a Instance in a public subnet after stopped and started in case of attached 2 eni.
Problem Description: It isn’t re-assigned a public IP address and public IP DNS for a Instance in a public subnet after stopped and started in case of attached 2 eni.
Symptom with screenshot
Step 1. Initialized Instance
Step 2. Stopped Instance
Step 3. Re-Started Instance
Step 4. Rebooted Instance
Question #1. Is that normal?
Question #2. Why it isn’t re-assigned a public IP address and public IP DNS with this case
Question #3. How I can prevent with re-assigned public IP address and public IP DNS with this this case
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
See below 2 points from the documentation; what you are seeing is expected behavior. You can use Elastic IP instead of Public IP if you want persistent behavior.
-
We release your instance's public IP address when it is stopped, hibernated, or terminated. Your stopped or hibernated instance receives a new public IP address when it is started.
-
You cannot auto-assign a public IP address if you specify more than one network interface. Additionally, you cannot override the subnet setting using the auto-assign public IP feature if you specify an existing network interface for eth0.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 6 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
Thank you for your answers. Can I ask 2 more questions from your answers?
Why it can't be auto-assigned a public IP address in case of 2 more eni on an instance
Do you mean it will keep the elastic IP on the primary eni although it has 2 more eni?
Think of Public IP as ephemeral entity (temp) if you want persistent IP use Elastic IP which you can attach/detach to any of the ENI on-demand.