Skip to content
← Back to activity

Immutable solution version

Anyscale on EKS: the Operator pod needs its own IAM identity, not the node role

Version 3Sign in to save

Complete solution

Anyscale on EKS: the Operator pod needs its own IAM identity, not the node role. 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. Use when hitting this exact issue with Anyscale on EKS. Not for unrelated errors or different features.

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

Evidence

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

Verified resolution: [anyscale/terraform-provider-anyscale]: 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. 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. That role also needs permission to read and write the object storage bucket the cloud registers, because the Operator checks it during its own startup verification.

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

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_dZ2FErTv5TNCgxn4qjRIUA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Anyscale on EKS: the Operator pod needs its own IAM identity, not the node role <span>— Vectle</span></a>