InfraScan Cloud

Repository scan

vishwakarma

getamis/vishwakarma · branch main · scanned 18 Feb 2026 · 139 resources

FOverall
FSecurity
–Reliability · N/A
DCost
207findings · 0 critical, 7 high
—no cost findings with a savings estimate

High 7

High Missing AWS Budget Cost · 6 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

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 189

Medium Ensure Terraform module sources use a commit hash Security · 47 places
Medium Ensure every security group and rule has a description Security · 38 places
Medium Old Generation Storage (gp2) Cost · 11 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 7 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 7 places
Medium Missing Spot Instance Usage Cost · 7 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 Instance Metadata Service Version 1 is not enabled Security · 6 places
Medium Missing Cost and Usage Report Cost · 6 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 IAM policies does not allow write access without constraints Security · 5 places
Medium Ensure that Security Groups are attached to another resource Security · 4 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 detailed monitoring is enabled for EC2 instances Security · 3 places
Medium Ensure that EC2 is EBS optimized 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 the S3 bucket has access logging enabled 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 that only encrypted EBS volumes are attached to EC2 instances Security · 2 places

Ensure that only encrypted EBS volumes are attached to EC2 instances

Documentation

Where

Medium Route53 A Record has Attached Resource Security · 2 places
Medium Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK) Security · 2 places

Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK)

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 all data stored in the EBS is securely encrypted Security · 2 places

Ensure all data stored in the EBS is securely encrypted

Documentation

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 S3 bucket has a Public Access block Security · 1 place

Ensure that S3 bucket has a Public Access block

Documentation

Where

Medium Ensure access control lists for S3 buckets are disabled Security · 1 place

Ensure access control lists for S3 buckets are disabled

Documentation

Where

Medium Ensure IAM policies does not allow credentials exposure Security · 1 place

Ensure IAM policies does not allow credentials exposure

Documentation

Where

Medium Ensure IAM policies does not allow data exfiltration Security · 1 place

Ensure IAM policies does not allow data exfiltration

Documentation

Where

Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 1 place

Ensure IAM policies does not allow permissions management / resource exposure without constraints

Documentation

Where

Medium Ensure IAM policies does not allow privilege escalation Security · 1 place

Ensure IAM policies does not allow privilege escalation

Documentation

Where

Medium Ensure that Elastic Load Balancer(s) uses SSL certificates provided by AWS Certificate Manager Security · 1 place

Ensure that Elastic Load Balancer(s) uses SSL certificates provided by AWS Certificate Manager

Documentation

Where

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

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

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 AWS Elastic Load Balancer listener uses TLS/SSL Security · 1 place

Ensure AWS Elastic Load Balancer listener uses TLS/SSL

Documentation

Where

Medium EC2 instance should not have public IP. Security · 1 place

EC2 instance should not have public IP.

Documentation

Where

Medium Load Balancer for Single Instance Cost · 1 place

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

Low 11

Low Large Root Volume Cost · 10 places
Low Elastic IP Usage 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 18 Feb 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.