public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-05 20:53:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update the permissions for EKS (#689)

Browse Source 
* docs: update the permissions for EKS

Added a missing permission to the example policy as this is required by
the eks-operator to cleanly delete a cluster.

Signed-off-by: Richard Case <richard.case@suse.com>

* syncing with versioned docs + canonical links

---------

Signed-off-by: Richard Case <richard.case@suse.com>
Co-authored-by: martyav <marty.avedon@suse.com>
This commit is contained in:
Richard Case
2023-06-29 22:26:29 +01:00
committed by GitHub
parent fdebc8fcc1
commit a46ff028e1
6 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/reference-guides/amazon-eks-permissions/minimum-eks-permissions.md
+5
View File
@@ -2,6 +2,10 @@
title: Minimum EKS Permissions
---
<head>
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks"/>
</head>
Documented here is a minimum set of permissions necessary to use all functionality of the EKS driver in Rancher. Additional permissions are required for Rancher to provision the `Service Role` and `VPC` resources. Optionally these resources can be created **before** the cluster creation and will be selectable when defining the cluster configuration.
Resource | Description
@@ -37,6 +41,7 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
"ec2:DescribeAvailabilityZones",
"ec2:DescribeAccountAttributes",
"ec2:DeleteTags",
"ec2:DeleteLaunchTemplate",
"ec2:DeleteSecurityGroup",
"ec2:DeleteKeyPair",
"ec2:CreateTags",