- 最新
- 投票最多
- 评论最多
Hello.
As @Steve_M says, you can't disable automatic public IPv4 for EC2 that's already up and running.
So, if you currently want to disable it, as answered at the URL below, create an AMI from an existing EC2 and configure it so that public IPv4 is not set when launching a new EC2 from that AMI.
https://repost.aws/questions/QUVmpO9BWGSuGwQh5tXk3f5w/how-to-remove-ipv4-public-ip-address-from-ec2-instances-before-february-2024-ipv6#ANm63x9ElRQDysJmJxm_zw5A
The only way the public IP address can be released is if the instance is stopped or hibernated, or if an elastic IP becomes associated with the instance.
Otherwise it doesn't appear this is possible.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
You cannot manually associate or disassociate a public IP (IPv4) address from your instance.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Exactly. I disabled auto ipv4 assignment and made a new instance with ipv6 only, using the root volume from the previous instance, so there's only internal ipv4 and a public ipv6. However, be careful, a lot of stuff doesn't seem to be working well with ipv6 on AWS, for example SES. It's such a pain to deal with IPv6, especially if AWS ain't even ready themselves.