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/guide/targetgroupbinding/targetgroupbinding.md
+53Lines changed: 53 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,6 +118,59 @@ The way to do that is assuming a role from such account. The following spec fiel
118
118
* `assumeRoleExternalId`: the external ID for the assume role operation. Optional, but recommended. It helps you to prevent the confused deputy problem ( https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html )
In order to use this feature, the source account (The cluster owner) must allow the controller role to assume role. By default, the installed permissions
145
+
_do not_ allow this. Augment the load balancer controller role by adding:
146
+
147
+
```json
148
+
{
149
+
"Effect": "Allow",
150
+
"Action": [
151
+
"sts:AssumeRole"
152
+
],
153
+
"Resource": "*"
154
+
}
155
+
```
156
+
157
+
In the target account, which owns the Target Group the assumed role must allow for Target Group Management, at the minimum:
0 commit comments