InfraScan Cloud

Repository scan

capillaries

capillariesio/capillaries · branch main · scanned 25 Jun 2026 · 48 resources

COverall
CSecurity
–Reliability · N/A
CCost
57findings · 0 critical, 1 high
$78.65–$160estimated 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 55

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 9 places
Medium Ensure that EC2 is EBS optimized Security · 9 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 9 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 9 places
Medium Missing Spot Instance Usage Cost · 3 places

No spot instances detected. Spot instances can save 50-90% on compute costs for interruptible workloads.

How to fix

Use spot instances for batch jobs, data analysis, and optional tasks. Consider aws_spot_instance_request or spot_price in launch templates.

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 that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 1 place

Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances

Documentation

Where

Medium Ensure that S3 bucket has a Public Access block Security · 1 place

Ensure that S3 bucket has a Public Access block

Documentation

Where

Medium Ensure that an S3 bucket has a lifecycle configuration Security · 1 place

Ensure that an S3 bucket has a lifecycle configuration

Documentation

Where

Medium Ensure S3 buckets should have event notifications enabled Security · 1 place

Ensure S3 buckets should have event notifications enabled

Documentation

Where

Medium Ensure that S3 bucket has cross-region replication enabled Security · 1 place

Ensure that S3 bucket has cross-region replication enabled

Documentation

Where

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 1 place

Ensure that S3 buckets are encrypted with KMS by default

Documentation

Where

Medium Ensure the S3 bucket has access logging enabled Security · 1 place

Ensure the S3 bucket has access logging enabled

Documentation

Where

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 1 place

Ensure all data stored in the S3 bucket have versioning enabled

Documentation

Where

Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 1 place

Ensure no security groups allow ingress from 0.0.0.0:0 to port 22

Documentation

Where

Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 1 place

Ensure no security groups allow ingress from 0.0.0.0:0 to port 80

Documentation

Where

Medium Ensure Terraform module sources use a commit hash Security · 1 place

Ensure Terraform module sources use a commit hash

Documentation

Where

Medium Ensure Terraform module sources use a tag with a version number Security · 1 place

Ensure Terraform module sources use a tag with a version number

Documentation

Where

Medium Missing S3 Lifecycle Policy Cost · 1 place

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 · 1 place

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

Low 1

Low Unassociated Elastic IP Cost · 1 place

Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.

How to fix

Release unattached Elastic IPs.

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.