Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update creating-a-vpc.md #780

Closed
wants to merge 1 commit into from
Closed

Update creating-a-vpc.md #780

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 1 addition & 13 deletions doc_source/creating-a-vpc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,18 +58,6 @@ You can also assign `IPv6` addresses to nodes in public and private subnets\. Th

1. Record the **SubnetIds** for the subnets that were created and whether you created them as public or private subnets\. You need at least two of these when you create your cluster and nodes\.

1. If you created an `IPv4` VPC, skip this step\. If you created an `IPv6` VPC, you must enable the auto\-assign `IPv6` address option for the public subnets that were created by the template\. That setting is already enabled for the private subnets\. To enable the setting, complete the following steps:

1. Open the Amazon VPC console at [https://console\.aws\.amazon\.com/vpc/](https://console.aws.amazon.com/vpc/)\.

1. In the left navigation pane, choose **Subnets**

1. Select one of your public subnets \(***stack\-name*/SubnetPublic01** or ***stack\-name*/SubnetPublic02** contains the word **public**\) and choose **Actions**, **Edit subnet settings**\.

1. Choose the **Enable auto\-assign `IPv6` address** check box and then choose **Save**\.

1. Complete the previous steps again for your other public subnet\.

------
#### [ Only public subnets ]

Expand Down Expand Up @@ -150,4 +138,4 @@ This VPC has three private subnets that are deployed into different Availability

1. \(Optional\) Any cluster that you deploy to this VPC can assign private `IPv4` addresses to your Pods and services\. If you want deploy clusters to this VPC to assign private `IPv6` addresses to your Pods and services, make updates to your VPC, subnet, route tables, and security groups\. For more information, see [Migrate existing VPCs from `IPv4` to `IPv6`](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html) in the Amazon VPC User Guide\. Amazon EKS requires that your subnets have the `Auto-assign` `IPv6` addresses option enabled \(it's disabled by default\)\.

------
------