- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello AWS Customer,
The public IP addressing feature is only available during launch. And, whether you assign a public IP address to your instance during launch or not, as you know, you can associate an Elastic IP address with your instance after it's launched.[1]
Hope you will find this information useful. Please let me know if you have any further questions or concerns. I will be more than glad to assist you.
Best regards,
Jisoo K.
Short answer: You can't do that with a Public IP. But you can do it with an Elastic IP.
You can associate a Public IP with an instance during launch but not after launch. However, you can allocate an Elastic IP then associate it with your instance after launch. Should you wish to change the IP you can de-associate it; release the Elastic IP; obtain a new one and associate it with your instance.
@Brettski-AWS: both you and Jisoo_K gave me answer I needed. Since the answers are effectively identical, I've accepted the one that arrived first. I hope you find this fair. I tried to accept both, but unsuccessfully.
No problem! Glad we answered the question. To be fair, Jisoo_K was first by a few seconds. ;-)
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 7 Monaten
I am avoiding Elastic IP because my EC2 instances will be powered off most of the month. I estimate I will run each of them 30 hours per month. (equals $3.5 USD per instance per month. So, my only option is to re-create the instance (since I won't use Elastic IP)?
What you could do is write a small script that starts/stops your instance and at the same time allocates/deallocates the EIP. That way you're not recreating the instance and you'll get a new IP every time.