Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed 12th point from 'Public and Private subnets' section since 'AssignIpv6AddressOnCreation' is supported in public subnets in CFN.
Issue #, if available:
In the CFN template provided for VPC with public and private subnets (IPv4 and IPv6), e.g. https://s3.us-west-2.amazonaws.com/amazon-eks/cloudformation/2020-10-29/amazon-eks-ipv6-vpc-public-private-subnets.yaml a limitation has been mentioned -
"Note: AssignIpv6AddressOnCreation: true is required but a CFN limitation right now, need to add this manually"
Due to which we need to manually enable the auto-assign IPv6 address option for the public subnets that were created by the template (as per point 12)
Since this limitation has already been addressed by CFN, so 'AssignIpv6AddressOnCreation' property is supported in public subnets as well and hence manually performing this step is not required now
Description of changes:
'AssignIpv6AddressOnCreation: true'
in public subnets as well {See attachment for updated template EKS-IPv4-IPv6.txt }By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.