- 最新
- 最多得票
- 最多評論
In order to deassociate the public IPv4 address, kindly follow these steps below.
- Create an ENI and attach it to the instance.
- Allocate an Elastic IP address using the below doc[1]
- Associate the Elastic IP to the primary ENI that has the public IP of the instance[2].
- Refresh the browser page and observe the instance public IP has changed to the new Elastic IP address.
- Disassociate the Elastic IP address from the primary ENI by following the below doc[3]
- Refresh the browser page again, and observe the instance public IP has been removed.
- Release the Elastic IP[4] and detach the ENI attached by the step #1.
References:
[1] Elastic IP addresses - Allocate an Elastic IP address - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating
[2] Elastic IP addresses - Associate an Elastic IP address with an instance or network interface - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating
[3] Elastic IP addresses - Disassociate an Elastic IP address - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating-different
[4] Elastic IP addresses - Release an Elastic IP address - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-releasing
相關內容
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
In my experience, this will work as long as the instance isn't stopped and started. If it is, a public IP address will be assigned again to the primary ENI.
This method doesn't work. The public ip will be assigned again automatically after the instance stop and restart. Evene during the public ip removal, ipv6 internet sites access are ok, but ipv4 internet sites can't be accessed whthin the instance. How to fix that?