public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-27 13:38:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

editing nate's note

Browse Source
This commit is contained in:
Mark Bishop
2018-10-19 16:34:55 -07:00
parent 70561348ac
commit c4f6e91694
1 changed files with 15 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md
+15 -16
View File
@@ -7,23 +7,20 @@ aliases:
---
## Objectives
1. [Create an account with appropriate permissions](#give-appropriate-permissions)
<!-- TOC -->
Create (or give an existing) user appropriate permissions to create an EKS cluster.
- [1. Give Appropriate Permissions](#1-give-appropriate-permissions)
- [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key)
- [3. Create the EKS Cluster](#3-create-the-eks-cluster)
2. [Create an access key and secret key](#create-access-key-and-secret-key)
Create an access key and secret key to access Amazon Web Services (AWS) resources from Rancher.
<!-- /TOC -->
3. [Create the EKS Cluster](#create-the-eks-cluster)
Using the AWS account, create your Amazon Elastic Container Service for Kubernetes (EKS) cluster in Rancher.
## Give Appropriate Permissions
## 1. Give Appropriate Permissions
Make sure that the account you will be using to create the EKS cluster has the appropriate permissions. Referring to the official [EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/IAM_policies.html) for details.
## Create Access Key and Secret Key
## 2. Create Access Key and Secret Key
Use AWS to create an access key and client secret.
@@ -39,7 +36,7 @@ Use AWS to create an access key and client secret.
6. Record the **Access key ID** and **Secret access key**. You will need to use these in Rancher to create your EKS cluster.
## Create the EKS Cluster
## 3. Create the EKS Cluster
Use {{< product >}} to set up and configure your Kubernetes cluster.
@@ -59,9 +56,11 @@ Use {{< product >}} to set up and configure your Kubernetes cluster.
8. Specify any additional options (such as instance type or minimum and maximum number of nodes). Then click **Create**.
# Note on Public IP for Worker Notes
If you are specifying `Public IP for Worker Nodes` as `false`, be aware that you must specify a properly configured VPC and subnets (instances in the subnets must have a route to the internet in order to connect to the control plane).
For example, a VPC could be constructed with 2 pairs of subnets, a private set and a public set. The private set would have their route tables set up to point to a NAT set up in their public counterpart. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html).
{{< result_create-cluster >}}
# Note on Public IP for Worker Notes
If you specify `Public IP for Worker Nodes` as `false`, you must also specify a VPC with subnets that allow your instances to access the internet. This access is required so that your worker nodes can connect to the Kubernetes control plane.
One possible configuration solution is a VPC constructed with two subnets, a private set and a public set. The private set should have its route tables configured to point toward a NAT in the public set. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html).