InfraScan Cloud

Repository scan

eks-cluster

junchil/eks-cluster · branch main · scanned 25 Jun 2026 · 115 resources

COverall
DSecurity
–Reliability · N/A
BCost
234findings · 0 critical, 1 high
$25.40–$79.60estimated savings per month, from the code

High 1

High Expensive NAT Gateway Cost · 1 place

NAT Gateways are expensive managed services. Ensure they are strictly necessary.

How to fix

Consider using VPC Endpoints, NAT Instances for non-critical workloads, or share a single NAT Gateway across multiple subnets.

Where

Medium 231

Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 8 places
Medium Ensure that S3 bucket has a Public Access block Security · 7 places
Medium Ensure S3 buckets should have event notifications enabled Security · 7 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 7 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 7 places
Medium Ensure the S3 bucket has access logging enabled Security · 7 places
Medium Ensure every security group and rule has a description Security · 7 places
Medium Image Tag should be fixed - not latest or blank Security · 7 places
Medium Use read-only filesystem for containers where possible Security · 7 places
Medium Minimize the admission of containers with the NET_RAW capability Security · 7 places
Medium Ensure that the seccomp profile is set to docker/default or runtime/default Security · 7 places
Medium Minimize the admission of containers with capabilities assigned Security · 7 places
Medium Ensure that Service Account Tokens are only mounted where necessary Security · 7 places
Medium Containers should run as a high UID to avoid host conflict Security · 7 places
Medium Image should use digest Security · 7 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 6 places
Medium CPU requests should be set Reliability · 6 places
Medium CPU limits should be set Reliability · 6 places
Medium Memory requests should be set Reliability · 6 places
Medium Memory limits should be set Reliability · 6 places
Medium Containers should not run with allowPrivilegeEscalation Security · 6 places
Medium Minimize the admission of root containers Security · 6 places
Medium Apply security context to your pods and containers Security · 6 places
Medium Apply security context to your containers Security · 6 places
Medium Liveness Probe Should be Configured Reliability · 6 places
Medium Readiness Probe Should be Configured Reliability · 6 places
Medium Minimize the admission of pods which lack an associated NetworkPolicy Security · 5 places

Minimize the admission of pods which lack an associated NetworkPolicy

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 5 places
Medium Ensure that a user for the container has been created Security · 5 places
Medium Image Pull Policy should be Always Security · 5 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 4 places
Medium The default namespace should not be used Security · 3 places
Medium Ensure top-level permissions are not set to write-all Security · 2 places

Ensure top-level permissions are not set to write-all

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 2 places
Medium Ensure the base image uses a non latest version tag Security · 2 places

Ensure the base image uses a non latest version tag

Documentation

Where

Medium Missing S3 Lifecycle Policy Cost · 2 places

S3 bucket without lifecycle rules. Objects are retained indefinitely, increasing storage costs.

How to fix

Define lifecycle rules to transition objects to cheaper storage classes (e.g., Glacier) or delete them after a retention period.

Where

Medium Missing Cost and Usage Report Cost · 2 places

No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.

How to fix

Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.

Where

Medium Ensure VPC flow logging is enabled in all VPCs Security · 1 place

Ensure VPC flow logging is enabled in all VPCs

Documentation

Where

Medium Ensure the default security group of every VPC restricts all traffic Security · 1 place

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure an IAM role is attached to EC2 instance Security · 1 place

Ensure an IAM role is attached to EC2 instance

Documentation

Where

and 19 more groups with 19 findings

Low 2

Low Missing AWS Budget Cost · 2 places

No AWS budget configured. Budgets help monitor and control spending with alerts.

How to fix

Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.

Where

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 25 Jun 2026; it may have changed since.

Scan your own repository

InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.