-
In that case explanation is still incorrect.
Also it bothers me that available CIDRs in the VPCs are not mentioned, as they might be exhausted and it might’ve been implied. Normally on VPC allocation, if you plan ahead, you might use all the available addresses by assigning subnets.
Also you say that “because this feature is limited to Nitro EC2 instance type, the option that says <i style=”font-family: inherit; font-size: inherit;”>“Set up a new IPv6-only subnet with a large CIDR range. Associate the new subnet with the VPC then launch the instance.“ is incorrect in all cases.”. You might want to specify instance type or mention that it’s not Nitro, because solution is valid in a subset of cases where Nitro EC2 instance is used.
Also what is even meant by “associate subnet with VPC”? Can you even create a subnet outside of the VPC? You have to specify VPC before creation of the subnet: https://docs.aws.amazon.com/cli/latest/reference/ec2/create-subnet.html
Below are some relevant excerpts from the “AWS Certification Subject Matter Expert (SME) Item Writing” course.
