- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello
Instance types: IPv6 is supported on all instance types, except C1, M1, M2, M3, and T1.
you can also see Elastic network interfaces, T2 family ec2 support IPv6
Hello.
You can also add IPv6 using t2.micro by following the steps below.
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html#working-with-ipv6-addresses
Therefore, I think there is a problem with the following procedure, which involves moving to a different subnet.
I created a new Network Interface using the new Subnet.
I attempted to Attach the new NI to my existing EC2 t2.micro instance.
Hello, If you want to use an IPv6-only EC2 instance, you need to use instance types based on nitro. For specific details, please refer to this documentation.
[+] Introducing IPv6-only subnets and EC2 instances https://aws.amazon.com/cn/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/
[+] Instances built on the AWS Nitro System - https://docs.aws.amazon.com/zh_cn/ec2/latest/instancetypes/ec2-nitro-instances.html
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Ah, so that means I need both IPv4 and IPv6 network interfaces instead IPv6 only NI? Maybe that's what the OP wants? To reduce the cost of using public IPv4 address on his/her instances?