You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks.md
+33-86Lines changed: 33 additions & 86 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,16 +93,14 @@ This [tutorial](https://aws.amazon.com/blogs/opensource/managing-eks-clusters-ra
93
93
94
94
## Minimum EKS Permissions
95
95
96
-
These are the minimum set of permissions necessary to access the full functionality of Rancher's EKS driver. You'll need additional permissions for Rancher to provision the `Service Role` and `VPC` resources. If you create these resources **before** you create the cluster, they'll be available when you configure the cluster.
96
+
These are the minimum set of permissions necessary to access the full functionality of Rancher's EKS driver. These permissions allow Rancher to create the Service Role and Virtual Private Cloud (VPC) resources on the users' behalf, if necessary.
97
97
98
98
:::note
99
99
In EKS v1.23 and above, you must use the out-of-tree drivers for EBS-backed volumes. You need [specific permissions](#ebs-csi-driver-addon-permissions) to enable this add-on.
100
100
:::
101
101
102
102
Resource | Description
103
103
---------|------------
104
-
Service Role | Provides permissions that allow Kubernetes to manage resources on your behalf. Rancher can create the service role with the following [Service Role Permissions](#service-role-permissions).
105
-
VPC | Provides isolated network resources utilised by EKS and worker nodes. Rancher can create the VPC resources with the following [VPC Permissions](#vpc-permissions).
106
104
EBS CSI Driver add-on | Provides permissions that allow Kubernetes to interact with EBS and configure the cluster to enable the add-on (required for EKS v1.23 and above). Rancher can install the add-on with the following [EBS CSI Driver addon Permissions](#ebs-csi-driver-addon-permissions).
107
105
108
106
@@ -167,18 +165,23 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
167
165
"Sid": "IAMPermissions",
168
166
"Effect": "Allow",
169
167
"Action": [
168
+
"iam:AddRoleToInstanceProfile",
170
169
"iam:AttachRolePolicy",
170
+
"iam:CreateInstanceProfile",
171
171
"iam:CreateRole",
172
-
"iam:DetachRolePolicy",
172
+
"iam:CreateServiceLinkedRole",
173
+
"iam:DeleteInstanceProfile",
173
174
"iam:DeleteRole",
174
-
"iam:GetRole",
175
+
"iam:DetachRolePolicy",
175
176
"iam:GetInstanceProfile",
177
+
"iam:GetRole",
176
178
"iam:ListAttachedRolePolicies",
177
-
"iam:ListInstanceProfilesForRole",
178
179
"iam:ListInstanceProfiles",
180
+
"iam:ListInstanceProfilesForRole",
179
181
"iam:ListRoles",
180
182
"iam:ListRoleTags",
181
-
"iam:PassRole"
183
+
"iam:PassRole",
184
+
"iam:RemoveRoleFromInstanceProfile",
182
185
"iam:TagRole"
183
186
],
184
187
"Resource": "*"
@@ -199,6 +202,7 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
199
202
"eks:DeleteCluster",
200
203
"eks:DeleteFargateProfile",
201
204
"eks:DeleteNodegroup",
205
+
"eks:DescribeAddon",
202
206
"eks:DescribeCluster",
203
207
"eks:DescribeFargateProfile",
204
208
"eks:DescribeNodegroup",
@@ -216,41 +220,31 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
216
220
"eks:UpdateNodegroupVersion"
217
221
],
218
222
"Resource": "*"
219
-
}
220
-
]
221
-
}
222
-
```
223
-
224
-
### Service Role Permissions
225
-
226
-
These are permissions that are needed during EKS cluster creation, so Rancher can create a service role on the users' behalf.
Copy file name to clipboardExpand all lines: versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks.md
+33-86Lines changed: 33 additions & 86 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,16 +93,14 @@ This [tutorial](https://aws.amazon.com/blogs/opensource/managing-eks-clusters-ra
93
93
94
94
## Minimum EKS Permissions
95
95
96
-
These are the minimum set of permissions necessary to access the full functionality of Rancher's EKS driver. You'll need additional permissions for Rancher to provision the `Service Role` and `VPC` resources. If you create these resources **before** you create the cluster, they'll be available when you configure the cluster.
96
+
These are the minimum set of permissions necessary to access the full functionality of Rancher's EKS driver. These permissions allow Rancher to create the Service Role and Virtual Private Cloud (VPC) resources on the users' behalf, if necessary.
97
97
98
98
:::note
99
99
In EKS v1.23 and above, you must use the out-of-tree drivers for EBS-backed volumes. You need [specific permissions](#ebs-csi-driver-addon-permissions) to enable this add-on.
100
100
:::
101
101
102
102
Resource | Description
103
103
---------|------------
104
-
Service Role | Provides permissions that allow Kubernetes to manage resources on your behalf. Rancher can create the service role with the following [Service Role Permissions](#service-role-permissions).
105
-
VPC | Provides isolated network resources utilised by EKS and worker nodes. Rancher can create the VPC resources with the following [VPC Permissions](#vpc-permissions).
106
104
EBS CSI Driver add-on | Provides permissions that allow Kubernetes to interact with EBS and configure the cluster to enable the add-on (required for EKS v1.23 and above). Rancher can install the add-on with the following [EBS CSI Driver addon Permissions](#ebs-csi-driver-addon-permissions).
107
105
108
106
@@ -167,18 +165,23 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
167
165
"Sid": "IAMPermissions",
168
166
"Effect": "Allow",
169
167
"Action": [
168
+
"iam:AddRoleToInstanceProfile",
170
169
"iam:AttachRolePolicy",
170
+
"iam:CreateInstanceProfile",
171
171
"iam:CreateRole",
172
-
"iam:DetachRolePolicy",
172
+
"iam:CreateServiceLinkedRole",
173
+
"iam:DeleteInstanceProfile",
173
174
"iam:DeleteRole",
174
-
"iam:GetRole",
175
+
"iam:DetachRolePolicy",
175
176
"iam:GetInstanceProfile",
177
+
"iam:GetRole",
176
178
"iam:ListAttachedRolePolicies",
177
-
"iam:ListInstanceProfilesForRole",
178
179
"iam:ListInstanceProfiles",
180
+
"iam:ListInstanceProfilesForRole",
179
181
"iam:ListRoles",
180
182
"iam:ListRoleTags",
181
-
"iam:PassRole"
183
+
"iam:PassRole",
184
+
"iam:RemoveRoleFromInstanceProfile",
182
185
"iam:TagRole"
183
186
],
184
187
"Resource": "*"
@@ -199,6 +202,7 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
199
202
"eks:DeleteCluster",
200
203
"eks:DeleteFargateProfile",
201
204
"eks:DeleteNodegroup",
205
+
"eks:DescribeAddon",
202
206
"eks:DescribeCluster",
203
207
"eks:DescribeFargateProfile",
204
208
"eks:DescribeNodegroup",
@@ -216,41 +220,31 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
216
220
"eks:UpdateNodegroupVersion"
217
221
],
218
222
"Resource": "*"
219
-
}
220
-
]
221
-
}
222
-
```
223
-
224
-
### Service Role Permissions
225
-
226
-
These are permissions that are needed during EKS cluster creation, so Rancher can create a service role on the users' behalf.
0 commit comments