InfraScan Cloud

Repository scan

springapp_terraform

ankit20000/springapp_terraform · branch main · scanned 25 Jun 2026 · 114 resources

DOverall
DSecurity
–Reliability · N/A
DCost
131findings · 0 critical, 12 high
$59.13–$267estimated savings per month, from the code

High 12

High Expensive NAT Gateway Cost · 6 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 Old Generation Instance Cost · 3 places

Usage of old generation EC2 instances (e.g., t2, m3, c4, r3). Newer generations are often cheaper and faster.

How to fix

Upgrade to current generation instances (e.g., t3, m5, c5, r5).

Where

High RDS Old Generation Instance Cost · 3 places

Usage of old generation RDS instance classes (db.t2, db.m3, db.m4, db.r3, db.r4). Newer generations are cheaper and faster.

How to fix

Upgrade to current generation instance classes (e.g., db.t3, db.m5, db.r5, db.r6g).

Where

Medium 117

Medium Ensure every security group and rule has a description Security · 8 places
Medium Ensure VPC subnets do not assign public IP by default Security · 6 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 5 places
Medium Ensure VPC flow logging is enabled in all VPCs Security · 3 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 3 places

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure that ALB redirects HTTP requests into HTTPS ones Security · 3 places
Medium Ensure public facing ALB are protected by WAF Security · 3 places
Medium Ensure that Security Groups are attached to another resource Security · 3 places
Medium Ensure that S3 bucket has a Public Access block Security · 3 places
Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 3 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 3 places
Medium Ensure S3 buckets should have event notifications enabled Security · 3 places
Medium Ensure that load balancer is using at least TLS 1.2 Security · 3 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 3 places

Ensure that enhanced monitoring is enabled for Amazon RDS instances

Documentation

Where

Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 3 places

Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 3 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 3 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 3 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 3 places
Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 3 places
Medium Ensure all data stored in the RDS is securely encrypted at rest Security · 3 places
Medium Ensure RDS database has IAM authentication enabled Security · 3 places
Medium Ensure all data stored in RDS is not publicly accessible Security · 3 places
Medium Ensure the S3 bucket has access logging enabled Security · 3 places
Medium Ensure ALB protocol is HTTPS Security · 3 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 3 places
Medium Ensure that AWS database instances have deletion protection enabled Reliability · 3 places

Ensure that AWS database instances have deletion protection enabled

Documentation

Where

Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 3 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 3 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 3 places

Ensure the ELBv2 (Application/Network) has access logging enabled

Documentation

Where

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 Load Balancer for Single Instance Cost · 3 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 Multiple NAT Gateways (Potential Redundancy) Cost · 3 places

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

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 2 places

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 · 2 places

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

Documentation

Where

Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 2 places

Ensure no security groups allow egress from 0.0.0.0:0 to port -1

Documentation

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

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.