# EKS Secrets on AWS | ZopNight

> Every check ZopNight runs on your EKS Secrets on AWS: 2 in total, across governance and security. Each one says why it matters and exactly what to change.

Source: https://zop.dev/zopnight/rules/aws/eks-secret

---

_AWS · 2 checks_

## EKS Secrets on AWS, checked for you.

ZopNight runs 2 checks on your EKS Secrets in AWS, covering governance and security. Workloads are scheduled by namespace.

- 2 — checks
- 2 — categories
- Manual — fixes, spelled out
- Yes — scheduled with its namespace

Free to start. No card. The playground just needs your work email.

## Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

### Governance

Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.

- [Secret Has Excessive Keys](https://zop.dev/zopnight/rules/secret-has-excessive-keys)

### Security

Risky configurations: privileged containers, containers running as root, host networking, ingress without TLS.

- [Legacy Service-Account-Token Secret](https://zop.dev/zopnight/rules/legacy-service-account-token-secret)

## Find these on your own EKS Secrets.

Connect a read-only role and ZopNight inventories the EKS Secrets you run, then runs all 2 checks against them.

[object Object]