From 9b3cee4da5b4d762b5940acf8e0c5d3cda4a7c1c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 19 Oct 2018 16:26:44 -0700 Subject: [PATCH] rewrite for amazon eks cluster provisioning. --- .../hosted-kubernetes-clusters/eks/_index.md | 55 +++++++++---------- 1 file changed, 27 insertions(+), 28 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index 7193162ff62..5534f6c5f0b 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -22,33 +22,23 @@ Make sure that the account you will be using to create the EKS cluster has the a ## 2. Create Access Key and Secret Key -Use AWS to create an access key and client secret. +Use AWS to create an access key and client secret for the IAM account used in [1. Give Appropriate Permissions](#1-give-appropriate-permissions). -1. In the AWS Console, go to the **IAM** service. - -2. Select **Users**. - -3. Find the user you wish to create the EKS cluster with. Select the user. - -4. Click **Security Credentials**. - -5. Click **Create access key**. - -6. Record the **Access key ID** and **Secret access key**. You will need to use these in Rancher to create your EKS cluster. +For instructions on how to create these keys, see the AWS documentation [Managing Access Keys: To create, modify, or delete a user's access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey). ## 3. Create the EKS Cluster -Use {{< product >}} to set up and configure your Kubernetes cluster. +Use Rancher to set up and configure your Kubernetes cluster. 1. From the **Clusters** page, click **Add Cluster**. -2. Choose **Amazon EKS**. +1. Choose **Amazon EKS**. -3. Enter a **Cluster Name**. +1. Enter a **Cluster Name**. -4. {{< step_create-cluster_member-roles >}} +1. {{< step_create-cluster_member-roles >}} -1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field. +1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field using the information obtained in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | Setting | Description | | ---------- | -------------------------------------------------------------------------------------------------------------------- | @@ -56,12 +46,12 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. | Access Key | Enter the access key that you created in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | | Secret Key | Enter the secret key that you created in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | -1. Click **Next: Select Service Role**. Then choose a service role. +1. Click **Next: Select Service Role**. Then choose a [service role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html). Service Role | Description -------------|--------------------------- - Standard: Rancher generated service role | placeholder - Custom: Choose from your existing service roles | placeholder + Standard: Rancher generated service role | If you choose this role, Rancher automatically adds a service role for use with the cluster. + Custom: Choose from your existing service roles | If you choose this role, Rancher lets you choose from service roles that you're already created within AWS. For more information on creating a custom service role in AWS, see the [Amazon documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#create-service-linked-role). 1. Click **Next: Select VPC and Subnet**. @@ -74,6 +64,10 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. 1. Now choose a **VPC & Subnet**. Follow one of the sets of instructions below based on your selection from the previous step. + Amazon Documentation: + + - [What Is Amazon VPC?](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html) + - [VPCs and Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html) {{% accordion id="yes" label="Public IP for Worker Nodes—Yes" %}} If you choose to assign a public IP address to your cluster's worker nodes, you have the option of choosing between a VPC that's automatically generated by Rancher (i.e., **Standard: Rancher generated VPC and Subnet**), or a VPC that you're already created with AWS (i.e., **Custom: Choose from your existing VPC and Subnets**). Choose the option that best fits your use case. @@ -83,11 +77,11 @@ If you choose to assign a public IP address to your cluster's worker nodes, you Option | Description -------|------------ Standard: Rancher generated VPC and Subnet | While provisioning your cluster, Rancher generates a new VPC and Subnet. - Custom: Choose from your exiting VPC and Subnets | While provisioning your cluster, Rancher configures your nodes to use a VPC and Subnet that you've already created in AWS. If you choose this option, complete the remaining steps below. + Custom: Choose from your exiting VPC and Subnets | While provisioning your cluster, Rancher configures your nodes to use a VPC and Subnet that you've already [created in AWS](https://docs.aws.amazon.com/vpc/latest/userguide/getting-started-ipv4.html). If you choose this option, complete the remaining steps below. 1. If you're using **Custom: Choose from your existing VPC and Subnets**: - (If you're using **Standard**, skip to [step 10](#security-group)) + (If you're using **Standard**, skip to [step 11](#select-instance-options)) 1. Make sure **Custom: Choose from your existing VPC and Subnets** is selected. @@ -109,16 +103,21 @@ If you chose this option, you must also choose a **VPC & Subnet** that allow you 1. Click **Next: Select Security Group**. {{% /accordion %}} -1. Choose a **Security Group**. +1. Choose a **Security Group**. See the documentation below on how to create one. -1. Click **Select Instance Options**, and then edit the node options available. + Amazon Documentation: + + - [Security Groups for Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) + - [Create a Security Group](https://docs.aws.amazon.com/vpc/latest/userguide/getting-started-ipv4.html#getting-started-create-security-group) + +1. Click **Select Instance Options**, and then edit the node options available. Option | Description -------|------------ - Instance Type | placeholder - Custom AMI Override | placeholder - Minimum ASG Size | placeholder - Maximum ASG Size | placeholder + Instance Type | Choose the [hardware specs](https://aws.amazon.com/ec2/instance-types/) for the instance you're provisioning. + Custom AMI Override | If you want to use a custom [Amazon Machine Image](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html#creating-an-ami) (AMI), specify it here. + Minimum ASG Size | The minimum number of instances that your cluster will scale to during low traffic, as controlled by [Amazon Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html). + Maximum ASG Size | The maximum number of instances that your cluster will scale to during high traffic, as controlled by [Amazon Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html). 1. Click **Create**.