AWS: Creation of load balancer fails due to missing policies

[vkurup]

When you run this role the first time on a stack that has no load balancers, the role succeeds but the load balancer is not created.

We believe this is because some permissions have not been given to the EKS service role that is automatically created (as described in this comment)

I was able to get around this by purging the ingress controller, adding this policy to the EKS service role in the IAM admin and then re-running the role:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeInternetGateways",
                "ec2:DescribeAddresses",
                "ec2:DescribeAccountAttributes"
            ],
            "Resource": "*"
        }
    ]
}

@copelco worked around it in a better way, by running this CLI command (source):

aws iam create-service-linked-role --aws-service-name "elasticloadbalancing.amazonaws.com"