Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.iru.com/llms.txt

Use this file to discover all available pages before exploring further.

​
About Amazon Elastic Kubernetes Service (EKS)

The Amazon EKS connector gathers cluster, node group, add-on, and access entry metadata exposed through the EKS AWS API (distinct from Kubernetes RBAC inside the data plane). Authentication is sts:AssumeRole into a customer role with eks:Describe* / eks:List* coverage.

​
How it works

There is no single AWS-managed “EKS read-only everything” policy for every API surface - start from the inline JSON below unless your platform team publishes a curated variant.
DetailValue
CategoryKubernetes control plane
AuthenticationCross-account IAM role

​
Prerequisites

  • IAM rights to manage roles.
  • At least one EKS cluster if you expect immediate inventory.

​
Connect AWS EKS to Iru

​
Copy the trust policy from Iru

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on AWS EKS

Find AWS EKS (use Category or Search by name or description). On that card, turn on the toggle. Leave the wizard tab open.
3

Copy the trust policy JSON

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::753695775620:role/IruConnect"
      },
      "Condition": {
        "StringEquals": {
          "sts:ExternalId": "YOUR_EXTERNAL_ID"
        }
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

​
Create the IAM role in AWS

1

Start Create role

Open IAM → Roles → Create role.
2

Configure trusted entity

Choose AWS account → Another AWS account. Enter 753695775620 (or the ID Iru shows). Enable Require external ID and paste the external ID from Iru.
3

Attach the EKS metadata inline policy

Add this inline policy:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "eks:Describe*",
        "eks:List*"
      ],
      "Resource": "*"
    }
  ]
}
4

Name the role and copy the ARN

Name the role (for example IruEKSReadOnly), create it, and copy the Role ARN.
5

Verify the trust relationship

Confirm Trust relationships matches the wizard JSON.

​
Submit the role ARN in Iru

1

Paste the IAM Role ARN

Paste the Role ARN into the connector where the wizard prompts for it.
2

Confirm the source is Active

Submit until AWS EKS shows Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
External ID mismatch.
New EKS APIs appear frequently - wildcards keep policies forward-compatible; tighten only with testing.

​
Considerations

This covers AWS-side EKS APIs: pod-level evidence…

This covers AWS-side EKS APIs - pod-level evidence still belongs to Kubernetes auditing/logging pipelines.

​
See also