@@ -46,6 +46,7 @@ cluster, the IAM user requires the following permissions:
46
46
* `ec2:DescribeNetworkAcls`
47
47
* `ec2:DescribeNetworkInterfaces`
48
48
* `ec2:DescribePrefixLists`
49
+ * `ec2:DescribePublicIpv4Pools` (only required if `publicIpv4Pool` is specified in `install-config.yaml`)
49
50
* `ec2:DescribeRegions`
50
51
* `ec2:DescribeRouteTables`
51
52
* `ec2:DescribeSecurityGroupRules`
@@ -58,6 +59,7 @@ cluster, the IAM user requires the following permissions:
58
59
* `ec2:DescribeVpcClassicLinkDnsSupport`
59
60
* `ec2:DescribeVpcEndpoints`
60
61
* `ec2:DescribeVpcs`
62
+ * `ec2:DisassociateAddress` (only required if `publicIpv4Pool` is specified in `install-config.yaml`)
61
63
* `ec2:GetEbsDefaultKmsKeyId`
62
64
* `ec2:ModifyInstanceAttribute`
63
65
* `ec2:ModifyNetworkInterfaceAttribute`
@@ -119,6 +121,7 @@ If you use an existing Virtual Private Cloud (VPC), your account does not requir
119
121
* `elasticloadbalancing:RegisterInstancesWithLoadBalancer`
120
122
* `elasticloadbalancing:RegisterTargets`
121
123
* `elasticloadbalancing:SetLoadBalancerPoliciesOfListener`
124
+ * `elasticloadbalancing:SetSecurityGroups`
122
125
123
126
[IMPORTANT]
124
127
=====
@@ -192,6 +195,7 @@ If you have not created a load balancer in your AWS account, the IAM user also r
192
195
* `s3:GetReplicationConfiguration`
193
196
* `s3:ListBucket`
194
197
* `s3:PutBucketAcl`
198
+ * `s3:PutBucketPolicy`
195
199
* `s3:PutBucketTagging`
196
200
* `s3:PutEncryptionConfiguration`
197
201
====
0 commit comments