InfraScan Cloud

Repository scan

gen3-terraform

uc-cdis/gen3-terraform · branch master · scanned 17 Jun 2026 · 1,263 resources

FOverall
FSecurity
–Reliability · N/A
FCost
1,231findings · 0 critical, 54 high
—no cost findings with a savings estimate

High 54

High Missing AWS Budget Cost · 44 places
High Old Generation Instance Cost · 7 places
High Expensive NAT Gateway Cost · 2 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 Unencrypted EBS Volume Cost · 1 place

EBS volume is not encrypted. This is a security risk and often indicates unmanaged infrastructure.

How to fix

Enable encryption for EBS volumes.

Where

Medium 1,167

Medium Ensure every security group and rule has a description Security · 65 places
Medium Missing Spot Instance Usage Cost · 62 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 32 places
Medium Ensure S3 buckets should have event notifications enabled Security · 30 places
Medium Ensure IAM policies does not allow write access without constraints Security · 30 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 30 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 30 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 29 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 29 places
Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 29 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 27 places
Medium Ensure the S3 bucket has access logging enabled Security · 23 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 22 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 20 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 19 places
Medium Ensure that S3 bucket has a Public Access block Security · 18 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 16 places
Medium Ensure that EC2 is EBS optimized Security · 16 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 14 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 14 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 14 places
Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 14 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 14 places
Medium Ensure that RDS instances have performance insights enabled Security · 14 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 14 places
Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 13 places
Medium Check encryption settings for Lambda environmental variable Security · 13 places
Medium Ensure IAM policies does not allow write access without constraints Security · 13 places
Medium Ensure Lambda Runtime is not deprecated Security · 13 places
Medium Ensure that respective logs of Amazon Relational Database Service (Amazon RDS) are enabled Security · 11 places
Medium Ensure that RDS instances have Multi-AZ enabled Reliability · 11 places
Medium Ensure that AWS database instances have deletion protection enabled Reliability · 11 places
Medium X-Ray tracing is enabled for Lambda Security · 10 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 9 places
Medium Ensure that VPC Flow Logs is enabled for every subnet in a VPC Network Security · 9 places
Medium Ensure Terraform module sources use a commit hash Security · 9 places
Medium Ensure an IAM role is attached to EC2 instance Security · 8 places
Medium Ensure that Security Groups are attached to another resource Security · 8 places
Medium Ensure Kinesis Firehose delivery stream is encrypted Security · 8 places
Medium Ensure that Kinesis Firehose Delivery Streams are encrypted with CMK Security · 8 places

and 138 more groups with 388 findings

Low 10

Low EC2 Detailed Monitoring Cost · 7 places
Low SQS Max Message Retention Cost · 2 places

SQS queue configured with the maximum 14-day (1209600 s) message retention. On high-volume queues this inflates storage costs and may indicate unprocessed message buildup.

How to fix

Set retention to the minimum business requirement (e.g., 1–4 days for most queues) and alert on queue depth to catch processing failures early.

Where

Low Large Root Volume Cost · 1 place

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 17 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.