InfraScan Cloud

Repository scan

provability-fabric

SentinelOps-CI/provability-fabric · branch main · scanned 25 Jun 2026 · 118 resources

DOverall
FSecurity
–Reliability · N/A
CCost
219findings · 0 critical, 3 high
$19.96–$82.55estimated savings per month, from the code

High 3

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

High Missing VPC Endpoints for S3/DynamoDB Cost · 1 place

NAT Gateway and S3/DynamoDB resources are present but no aws_vpc_endpoint is defined. All S3 and DynamoDB traffic is routed through the NAT Gateway, incurring per-GB data-processing charges ($0.045/GB).

How to fix

Add Gateway VPC Endpoints for S3 (com.amazonaws.<region>.s3) and DynamoDB (com.amazonaws.<region>.dynamodb). Gateway endpoints are free and eliminate NAT data-processing charges for these services.

Where

Medium 210

Medium Ensure top-level permissions are not set to write-all Security · 70 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 14 places
Medium The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. Security · 11 places
Medium Ensure that a user for the container has been created Security · 10 places
Medium Ensure VPC subnets do not assign public IP by default Security · 6 places
Medium Ensure every security group and rule has a description Security · 6 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 6 places
Medium Ensure the base image uses a non latest version tag Security · 6 places
Medium Ensure VPC flow logging is enabled in all VPCs Security · 4 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 4 places
Medium Ensure that S3 bucket has a Public Access block Security · 4 places
Medium Ensure RDS instance with copy tags to snapshots is enabled 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 enhanced monitoring is enabled for Amazon RDS instances Security · 4 places
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 4 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 4 places
Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 4 places
Medium Ensure RDS database has IAM authentication enabled Security · 4 places
Medium Ensure the S3 bucket has access logging enabled Security · 4 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 4 places
Medium Ensure that RDS instances have performance insights enabled Security · 4 places
Medium Ensure Postgres RDS as aws_db_instance has Query Logging enabled Security · 3 places
Medium Ensure public facing ALB are protected by WAF Security · 2 places
Medium Ensure that Security Groups are attached to another resource Security · 2 places

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 2 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 2 places

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

Documentation

Where

Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 2 places
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 Load Balancer for Single Instance Cost · 2 places

Load balancer detected. Verify it's needed - load balancers cost $15-20/month even if unused.

How to fix

Consider if load balancer is necessary for single-instance deployments or low-traffic applications.

Where

Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 1 place

Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones

Documentation

Where

Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 1 place

Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones

Documentation

Where

Medium Ensure that RDS instances has backup policy Reliability · 1 place

Ensure that RDS instances has backup policy

Documentation

Where

Medium Ensure that AWS database instances have deletion protection enabled Reliability · 1 place

Ensure that AWS database instances have deletion protection enabled

Documentation

Where

Medium Basic Auth Credentials Security · 1 place
Medium Multiple NAT Gateways (Potential Redundancy) Cost · 1 place

More than one aws_nat_gateway defined. In development or staging environments a single NAT Gateway is usually sufficient; multiple gateways add ~$32/month each plus data-processing fees.

How to fix

Verify that each additional NAT Gateway is needed for HA in production. For dev/staging environments consider consolidating to a single gateway.

Where

Low 6

Low Route53 Health Checks Cost · 4 places

Route53 health checks incur monthly costs. May not be necessary for all resources.

How to fix

Remove health checks for non-critical resources or personal projects.

Where

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.