Public IP (Primary IP) lost in AWS after attaching an additional network interface after adding it in AWS instance.
Page 1 of 1
Public IP (Primary IP) lost in AWS after attaching an additional network interface after adding it in AWS instance.
by Guest Thu Jan 07, 2021 5:09 am
After adding an additional network interface in AWS, I lost primary IP in AWS, when I hit “Attach”. It released the public IP. I don’t want this to happen.
Guest- Guest
Re: Public IP (Primary IP) lost in AWS after attaching an additional network interface after adding it in AWS instance.
by Guest Thu Jan 07, 2021 5:09 am
Please do following
1 - Create a new Network Interface in the same subnet as your EC2 instance.
2 - Allocate a new Elastic IP for your VPC (if you haven't done so already).
3 - Associate the Elastic IP address with your new Network Interface (eni).
4 - Attach your new Network Interface to your EC2 instance.
1 - Create a new Network Interface in the same subnet as your EC2 instance.
2 - Allocate a new Elastic IP for your VPC (if you haven't done so already).
3 - Associate the Elastic IP address with your new Network Interface (eni).
4 - Attach your new Network Interface to your EC2 instance.
Guest- Guest
Similar topics» Network Interface - Realocate
» If the TDM network is bridging the two SIP carriers, is the SHAKEN certificate lost end to end?
» I lost my web password. How can I recover it?
» Primary Host Shutdown
» Additional documentation available -- TBwiki
» If the TDM network is bridging the two SIP carriers, is the SHAKEN certificate lost end to end?
» I lost my web password. How can I recover it?
» Primary Host Shutdown
» Additional documentation available -- TBwiki
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum