InfraScan Cloud

Repository scan

K8S-On-Cloud

VardyNg/K8S-On-Cloud · branch main · scanned 25 Jun 2026 · 535 resources

FOverall
FSecurity
–Reliability · N/A
DCost
914findings · 0 critical, 4 high
$2.10–$81.30estimated savings per month, from the code

High 4

High Expensive Instance Type Cost · 2 places

Usage of very large instance types (xlarge+). Ensure this capacity is actually needed.

How to fix

Review utilization metrics. Consider rightsizing or Spot Instances.

Where

High Expensive NAT Gateway Cost · 2 places

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 867

Medium Ensure Terraform module sources use a commit hash Security · 80 places

Ensure Terraform module sources use a commit hash

Documentation

Where

Medium Minimize the admission of containers with the NET_RAW capability Security · 51 places

Minimize the admission of containers with the NET_RAW capability

Documentation

Where

Medium Apply security context to your pods, deployments and daemon_sets Security · 51 places

Apply security context to your pods, deployments and daemon_sets

Documentation

Where

Medium Image should use digest Security · 51 places

Image should use digest

Documentation

Where

Medium Liveness Probe Should be Configured Reliability · 51 places

Liveness Probe Should be Configured

Documentation

Where

Medium Readiness Probe Should be Configured Reliability · 51 places

Readiness Probe Should be Configured

Documentation

Where

Medium The default namespace should not be used Security · 49 places

The default namespace should not be used

Documentation

Where

Medium Apply security context to your pods and containers Security · 49 places

Apply security context to your pods and containers

Documentation

Where

Medium CPU requests should be set Reliability · 40 places

CPU requests should be set

Documentation

Where

Medium CPU Limits should be set Reliability · 40 places

CPU Limits should be set

Documentation

Where

Medium Missing Cost and Usage Report Cost · 40 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 Memory Limits should be set Reliability · 39 places

Memory Limits should be set

Documentation

Where

Medium Image Pull Policy should be Always Security · 39 places

Image Pull Policy should be Always

Documentation

Where

Medium Memory requests should be set Reliability · 37 places

Memory requests should be set

Documentation

Where

Medium Image Tag should be fixed - not latest or blank Security · 29 places

Image Tag should be fixed - not latest or blank

Documentation

Where

Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 12 places
Medium Ensure every security group and rule has a description Security · 9 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 9 places
Medium Ensure IAM policies does not allow write access without constraints Security · 8 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 6 places
Medium Ensure IAM policies does not allow data exfiltration Security · 5 places
Medium Ensure that S3 bucket has a Public Access block Security · 4 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 4 places
Medium Ensure S3 buckets should have event notifications enabled Security · 4 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 4 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 4 places
Medium Ensure the S3 bucket has access logging enabled Security · 4 places
Medium Ensure resource is encrypted by KMS using a customer managed Key (CMK) Security · 3 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 3 places
Medium Missing S3 Lifecycle Policy Cost · 3 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 Ensure VPC flow logging is enabled in all VPCs Security · 2 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 2 places
Medium Minimize the admission of pods which lack an associated NetworkPolicy Security · 2 places

Minimize the admission of pods which lack an associated NetworkPolicy

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure IAM policies does not allow write access without constraints Security · 2 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 2 places
Medium EFS access points should enforce a root directory Security · 2 places
Medium EFS access points should enforce a user identity Security · 2 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 2 places
Medium Ensure EFS is securely encrypted Security · 2 places
Medium Ensure EKS Cluster has Secrets Encryption Enabled Security · 2 places

and 55 more groups with 68 findings

Low 43

Low Missing AWS Budget Cost · 40 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

Low Large Root Volume Cost · 2 places

Oversized root block device. Many workloads don't require large root volumes.

How to fix

Reduce root volume size to minimum required (typically 8-20 GB for most Linux instances).

Where

Low EC2 Detailed Monitoring Cost · 1 place

Detailed monitoring for EC2 instances incurs extra costs.

How to fix

Disable detailed monitoring if standard 5-minute metrics are sufficient.

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.