Skip to main content

Overview

OpenSRE investigates Amazon EKS clusters with your AWS credentials. It reads cluster, node group, and addon state from the EKS API, and reads pods, logs, events, deployments, namespaces, and nodes from the cluster’s Kubernetes API. It authenticates to Kubernetes with an STS-signed token, the same way aws eks get-token does, so no kubectl binary or kubeconfig file is needed. Every call is read-only.
Use this page for EKS clusters reached with AWS credentials. For any cluster reached with a kubeconfig (GKE, AKS, on-prem, kind, or EKS with a kubeconfig you already have), use the Kubernetes integration.

Prerequisites

  • The AWS integration configured and passing opensre integrations verify aws
  • An EKS cluster whose Kubernetes API endpoint is reachable from where OpenSRE runs
  • The IAM identity OpenSRE uses mapped to read-only Kubernetes permissions (see Kubernetes access)

Setup

EKS has no separate setup target. It uses the AWS integration’s credentials:
The EKS tools become available once the AWS connection is verified and the investigation names a cluster (cluster_name). Deployment and pod tools also need a deployment or pod_name; namespace defaults to every namespace where a tool allows it.

Credentials

IAM permissions

If you set AWS_ROLE_ARN, the identity running OpenSRE also needs sts:AssumeRole on that role.

Kubernetes access

IAM permissions only cover the EKS API. To read pods, logs, and events, the same IAM role must also be mapped to a Kubernetes identity, with an EKS access entry (recommended) or the aws-auth ConfigMap. A least-privilege read-only ClusterRole covering every EKS tool:
Bind it to the Kubernetes group or username your access entry assigns to the OpenSRE role.

Tools

Use cases

  • Finding which pods are crash-looping or OOMKilled, and why
  • Checking whether a rollout is stuck, with unavailable replicas
  • Spotting unhealthy nodes, degraded node groups, or a broken addon after an upgrade

Verify

eks is an alias for this check. A passing verify confirms AWS credentials only. Kubernetes access is checked when a Kubernetes API tool runs, so a missing access entry or RBAC binding shows up as an Unauthorized or Forbidden tool result.

Troubleshooting

Security

  • All EKS and Kubernetes calls are read-only.
  • The ClusterRole above does not grant access to secrets or configmaps; keep it that way unless you need it.
  • Prefer a dedicated IAM role for OpenSRE so its cluster access can be audited and revoked on its own.