Repository scan
Terraform-WP
acf0x/Terraform-WP · branch main · scanned 25 Jun 2026 · 78 resources
High 2
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 71
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 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 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 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 VPC subnets do not assign public IP by default
Ensure VPC subnets do not assign public IP by default
Where
Medium Ensure that Load Balancer has deletion protection enabled
Ensure that Load Balancer has deletion protection enabled
Where
Medium Ensure DB instance gets all minor upgrades automatically
Ensure DB instance gets all minor upgrades automatically
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 the ELBv2 (Application/Network) has access logging enabled
Ensure the ELBv2 (Application/Network) has access logging enabled
Where
Medium Load Balancer for Single Instance
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 CloudFront distribution has a response headers policy attached
Ensure CloudFront distribution has a response headers policy attached
Where
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability
Where
Medium Ensure Secrets Manager secrets should have automatic rotation enabled
Ensure Secrets Manager secrets should have automatic rotation enabled
Where
Medium Ensure that an S3 bucket has a lifecycle configuration
Medium Ensure S3 buckets should have event notifications enabled
Medium Ensure KMS key Policy is defined
Medium Ensure AWS Load Balancers use strong ciphers
Medium Ensure that load balancer is using at least TLS 1.2
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 that ALB drops HTTP headers
Medium Ensure that S3 bucket has cross-region replication enabled
Medium Ensure that S3 buckets are encrypted with KMS by default
Medium Ensure that RDS instances have Multi-AZ enabled
Medium Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher
Verify CloudFront Distribution Viewer Certificate is using TLS v1.2 or higher
Where
Medium Ensure the S3 bucket has access logging enabled
Medium Ensure resource is encrypted by KMS using a customer managed Key (CMK)
Ensure resource is encrypted by KMS using a customer managed Key (CMK)
Where
Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)
Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)
Where
Medium Ensure Create before destroy for ACM certificates
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at rest
Ensure all data stored in the ElastiCache Replication Group is securely encrypted at rest
Where
Medium Ensure IAM policies does not allow write access without constraints
Ensure IAM policies does not allow write access without constraints
Where
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit
Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit
Where
Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token
Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token
Where
Medium Ensure CloudFront distributions should have origin failover configured
Ensure CloudFront distributions should have origin failover configured
Where
Medium Ensure CloudFront distribution ViewerProtocolPolicy is set to HTTPS
Ensure CloudFront distribution ViewerProtocolPolicy is set to HTTPS
Where
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions
Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions
Where
Medium Ensure AWS CloudFront web distribution has geo restriction enabled
Ensure AWS CloudFront web distribution has geo restriction enabled
Where
and 7 more groups with 7 findings
Low 1
Low Missing AWS Budget
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.