@@ -46,6 +46,7 @@ cluster, the IAM user requires the following permissions:
4646* `ec2:DescribeNetworkAcls`
4747* `ec2:DescribeNetworkInterfaces`
4848* `ec2:DescribePrefixLists`
49+ * `ec2:DescribePublicIpv4Pools` (only required if `publicIpv4Pool` is specified in `install-config.yaml`)
4950* `ec2:DescribeRegions`
5051* `ec2:DescribeRouteTables`
5152* `ec2:DescribeSecurityGroupRules`
@@ -58,6 +59,7 @@ cluster, the IAM user requires the following permissions:
5859* `ec2:DescribeVpcClassicLinkDnsSupport`
5960* `ec2:DescribeVpcEndpoints`
6061* `ec2:DescribeVpcs`
62+ * `ec2:DisassociateAddress` (only required if `publicIpv4Pool` is specified in `install-config.yaml`)
6163* `ec2:GetEbsDefaultKmsKeyId`
6264* `ec2:ModifyInstanceAttribute`
6365* `ec2:ModifyNetworkInterfaceAttribute`
@@ -119,6 +121,7 @@ If you use an existing Virtual Private Cloud (VPC), your account does not requir
119121* `elasticloadbalancing:RegisterInstancesWithLoadBalancer`
120122* `elasticloadbalancing:RegisterTargets`
121123* `elasticloadbalancing:SetLoadBalancerPoliciesOfListener`
124+ * `elasticloadbalancing:SetSecurityGroups`
122125
123126[IMPORTANT]
124127=====
@@ -192,6 +195,7 @@ If you have not created a load balancer in your AWS account, the IAM user also r
192195* `s3:GetReplicationConfiguration`
193196* `s3:ListBucket`
194197* `s3:PutBucketAcl`
198+ * `s3:PutBucketPolicy`
195199* `s3:PutBucketTagging`
196200* `s3:PutEncryptionConfiguration`
197201====
0 commit comments