## TL;DR

The fix is an EKS Pod Identity association with a dedicated role trusted by pods.eks.amazonaws.com, bound to the Operator's namespace and service account. The Operator runs as a pod, not an EC2 instance, so it cannot reuse the node group's IAM role: that role's trust policy only allows ec2.amazonaws.com to assume it, not pods.eks.amazonaws.com.

## Fix

1. The fix is an EKS Pod Identity association with a dedicated role trusted by pods.eks.amazonaws.com, bound to the Operator's namespace and service account.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Anyscale on EKS feature.
- The symptom matches: the Operator pod needs its own IAM identity, not the node role.

## When NOT to use

- Unrelated Anyscale on EKS issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Anyscale on EKS. Source: https://github.com/anyscale/terraform-provider-anyscale/blob/HEAD/docs/guides/create-a-kubernetes-cloud.md.

## Variant phrasings

### the Operator pod needs its own IAM identity, not the node role

## Why it happens

The Anyscale Operator fails to start with an IMDS or credentials error that has nothing obviously to do with IAM trust policies.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/anyscale/terraform-provider-anyscale/blob/HEAD/docs/guides/create-a-kubernetes-cloud.md