No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi, has anyone got Cluster autoscaler up and running with EKS? I'm running into this error when trying to create the cluster autoscaler role
```creating IAM Role (my_eks_cluster_autoscaler_role): MalformedPolicyDocument: This policy contains invalid Json```

here is the relevant Python function:
```def create_autoscaling_role(
    oidc_provider_arn,
    oidc_provider_url,
    oidc_iam_policy,
    cluster_autoscaler_iam_policy,
    cluster_name,
):
    oidc_iam_policy = oidc_iam_policy.render(
        cluster_oidc_provider_arn=oidc_provider_arn,
        cluster_oidc_provider_url=oidc_provider_url,
    )
    iam_policy = cluster_autoscaler_iam_policy.render(cluster_name=cluster_name)
    cluster_autoscaler_iam_role = aws.iam.Role(
        resource_name=f"{cluster_name}_cluster_autoscaler_role",
        name=f"{cluster_name}_cluster_autoscaler_role",
        assume_role_policy=json.dumps(oidc_iam_policy),
    )
    cluster_autoscaler_iam_policy = aws.iam.Policy(
        resource_name=f"{cluster_name}_cluster_autoscaler_policy",
        name=f"{cluster_name}_cluster_autoscaler_policy",
        policy=iam_policy,
    )
    aws.iam.RolePolicyAttachment(
        resource_name=f"{cluster_name}_cluster_autoscaler_policy_attachment",
        role=cluster_autoscaler_iam_role.name,
        policy_arn=cluster_autoscaler_iam_policy.arn,
    )
    return cluster_autoscaler_iam_role```


The json for the Trust Policy supplied to this line `assume_role_policy=json.dumps(oidc_iam_policy),`  is:
```    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Principal": {
                    "Federated": "arn:aws:iam::152*****449:oidc-provider/oidc.eks.ca-central-1.amazonaws.com/id/FE5D241***************"
                },
                "Action": "sts:AssumeRoleWithWebIdentity",
                "Condition": {
                    "StringEquals": {
                    "<http://oidc.eks.ca-central-1.amazonaws.com/id/FE5D241***************:aud|oidc.eks.ca-central-1.amazonaws.com/id/FE5D241***************:aud>": "<http://sts.amazonaws.com|sts.amazonaws.com>"
                    }
                }
            }
        ]
    }```

which exactly matches the json when creating the same via the AWS Console.

changing this line `assume_role_policy=json.dumps(oidc_iam_policy),` to `assume_role_policy=oidc_iam_policy,` , i.e passing the Jinja2 rendered string seemed to suffice. Issue resolved.