Repository scan
sumaform
uyuni-project/sumaform · branch main · scanned 4 Mar 2026 · 85 resources
High 1
High Expensive NAT Gateway
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 35
Medium Ensure that Security Groups are attached to another resource
Ensure that Security Groups are attached to another resource
Where
Medium Ensure VNET subnet is configured with a Network Security Group (NSG)
Ensure VNET subnet is configured with a Network Security Group (NSG)
Where
Medium Ensure every security group and rule has a description
Ensure every security group and rule has a description
Where
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Ensure no security groups allow egress from 0.0.0.0:0 to port -1
Where
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances
Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances
Where
Medium Missing Spot Instance Usage
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
Ensure VPC flow logging is enabled in all VPCs
Where
Medium Ensure the default security group of every VPC restricts all traffic
Ensure the default security group of every VPC restricts all traffic
Where
Medium Ensure that only encrypted EBS volumes are attached to EC2 instances
Ensure that only encrypted EBS volumes are attached to EC2 instances
Where
Medium Route53 A Record has Attached Resource
Route53 A Record has Attached Resource
Where
Medium Ensure RDS instance with copy tags to snapshots is enabled
Ensure RDS instance with copy tags to snapshots is enabled
Where
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances
Ensure that enhanced monitoring is enabled for Amazon RDS instances
Where
Medium Ensure that detailed monitoring is enabled for EC2 instances
Ensure that detailed monitoring is enabled for EC2 instances
Where
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled
Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled
Where
Medium Ensure VPC subnets do not assign public IP by default
Ensure VPC subnets do not assign public IP by default
Where
Medium Ensure that EC2 is EBS optimized
Medium Ensure that RDS instances have Multi-AZ enabled
Ensure that RDS instances have Multi-AZ enabled
Where
Medium Ensure all data stored in the RDS is securely encrypted at rest
Ensure all data stored in the RDS is securely encrypted at rest
Where
Medium Ensure DB instance gets all minor upgrades automatically
Ensure DB instance gets all minor upgrades automatically
Where
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22
Ensure no security groups allow ingress from 0.0.0.0:0 to port 22
Where
Medium Ensure that AWS database instances have deletion protection enabled
Ensure that AWS database instances have deletion protection enabled
Where
Medium Ensure that RDS instances have performance insights enabled
Ensure that RDS instances have performance insights enabled
Where
Medium Ensure Instance Metadata Service Version 1 is not enabled
Ensure Instance Metadata Service Version 1 is not enabled
Where
Medium Ensure Virtual Machine Extensions are not Installed
Ensure Virtual Machine Extensions are not Installed
Where
Low 4
Low Elastic IP Usage
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
Low Large Root Volume
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
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 4 Mar 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.