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

```
aws:route53:Record (Dev-Eks-nodeInternalElbDns):
    error: Plan apply failed: AccessDenied: User: &lt;arn&gt; is not authorized to access this resource
        status code: 403, request id: ba3a64a7-d984-4bd7-be97-12624890e903
```

Are you using the correct credentials or `$AWS_PROFILE`?

Yes. Everything works - creating eks cluster, node group, ingress, load balancer -  up to trying to create a dns record for the load balancer.

You may get more information from the error running with `TF_LOG=DEBUG pulumi up --debug --logtostderr`

Thanks. That gives me the actual call that's failing: route53/GetHostedZone.

`aws route53 get-hosted-zone --id &lt;id&gt;` fails too, so investigating further.