# EKS Ingresses on AWS | ZopNight

> Every check ZopNight runs on your EKS Ingresses on AWS: 2 in total, across reliability and security.

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

---

_AWS · 2 checks_

## EKS Ingresses on AWS, checked for you.

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

### Reliability

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

- [Ingress Has No Address](https://zop.dev/zopnight/rules/ingress-has-no-address)

### Security

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

- [Ingress Without TLS](https://zop.dev/zopnight/rules/ingress-without-tls)

## Find these on your own EKS Ingresses.

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

[object Object]