From 62141f0a0d2854a0a52a918101629fbdb6a5f46e Mon Sep 17 00:00:00 2001 From: Eamon Bauman Date: Wed, 23 Oct 2019 13:51:19 -0500 Subject: [PATCH] Clarifying there are no RKE config options Seems small, but can be misleading. There are plenty of options in AWS for configuring permission, etc. But in RKE, there is only one option and that is setting the name of the cloud provider. --- .../rke/latest/en/config-options/cloud-providers/aws/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rke/latest/en/config-options/cloud-providers/aws/_index.md b/content/rke/latest/en/config-options/cloud-providers/aws/_index.md index 278a54b1230..9ab6c05524d 100644 --- a/content/rke/latest/en/config-options/cloud-providers/aws/_index.md +++ b/content/rke/latest/en/config-options/cloud-providers/aws/_index.md @@ -3,7 +3,7 @@ title: AWS Cloud Provider weight: 251 --- -To enable the AWS cloud provider, there are no configuration options. You only need to set the name as `aws`. In order to use the AWS cloud provider, all cluster nodes must have already been configured with an [appropriate IAM role](#iam-requirements) and your AWS resources must be [tagged with a cluster ID](#tagging-amazon-resources). +To enable the AWS cloud provider, there are no RKE configuration options. You only need to set the name as `aws`. In order to use the AWS cloud provider, all cluster nodes must have already been configured with an [appropriate IAM role](#iam-requirements) and your AWS resources must be [tagged with a cluster ID](#tagging-amazon-resources). ```yaml cloud_provider: