# EKS Storage Classes on AWS | ZopNight

> Every check ZopNight runs on your EKS Storage Classes on AWS: 2 in total, across governance and reliability.

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

---

_AWS · 2 checks_

## EKS Storage Classes on AWS, checked for you.

ZopNight runs 2 checks on your EKS Storage Classes in AWS, covering governance and reliability. 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.

- [StorageClass Disallows Volume Expansion](https://zop.dev/zopnight/rules/storageclass-disallows-volume-expansion)

### Reliability

Production-shape issues that cause incidents and rework: single replicas, missing requests and limits, missing probes.

- [StorageClass Uses Immediate Binding](https://zop.dev/zopnight/rules/storageclass-uses-immediate-binding)

## Find these on your own EKS Storage Classes.

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

[object Object]