InfraScan Cloud

Repository scan

deployex

thiagoesteves/deployex · branch main · scanned 25 Jun 2026 · 166 resources

DOverall
FSecurity
–Reliability · N/A
CCost
199findings · 0 critical, 1 high
$123–$250estimated savings per month, from the code

High 1

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 197

Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 28 places

Ensure Secrets Manager secrets should have automatic rotation enabled

Documentation

Where

Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 28 places

Ensure that Secrets Manager secret is encrypted using KMS CMK

Documentation

Where

Medium Ensure every security group and rule has a description Security · 15 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 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 · 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 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 detailed monitoring is enabled for EC2 instances Security · 4 places
Medium Ensure that EC2 is EBS optimized Security · 4 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 4 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 4 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 4 places
Medium Ensure the S3 bucket has access logging enabled Security · 4 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 4 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 4 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 4 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 4 places
Medium Missing S3 Lifecycle Policy Cost · 4 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 Spot Instance Usage Cost · 4 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 access is controlled through SSO and not AWS IAM defined users Security · 3 places
Medium Ensure IAM policies does not allow write access without constraints Security · 3 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 3 places
Medium Ensure that CloudWatch Log Group specifies retention days Security · 3 places
Medium Ensure all data stored in the Launch configuration or instance Elastic Blocks Store is securely encrypted Security · 3 places
Medium EC2 instance should not have public IP. Security · 3 places
Medium CloudWatch Logs Without Retention Cost · 3 places

CloudWatch log group without retention_in_days. Logs are kept indefinitely by default, silently growing to hundreds $/month.

How to fix

Set appropriate retention periods for log groups (e.g., 7, 14, or 30 days).

Where

Medium Ensure public facing ALB are protected by WAF Security · 1 place
Medium Ensure that Security Groups are attached to another resource Security · 1 place

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 1 place

Ensure RDS instance with copy tags to snapshots is enabled

Documentation

Where

Medium Ensure AWS RDS database instance configured with encryption in transit Security · 1 place

Ensure AWS RDS database instance configured with encryption in transit

Documentation

Where

Medium Ensure AWS Load Balancers use strong ciphers Security · 1 place
Medium Ensure that load balancer is using at least TLS 1.2 Security · 1 place

Ensure that load balancer is using at least TLS 1.2

Documentation

Where

Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 1 place

Ensure that enhanced monitoring is enabled for Amazon RDS instances

Documentation

Where

Medium Ensure that ALB drops HTTP headers Security · 1 place
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 1 place

Ensure that Load Balancer has deletion protection enabled

Documentation

Where

Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 1 place
Medium Ensure RDS database has IAM authentication enabled Security · 1 place

Ensure RDS database has IAM authentication enabled

Documentation

Where

and 15 more groups with 15 findings

Low 1

Low Unassociated Elastic IP 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 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.