InfraScan Cloud

Repository scan

cyhy_amis

cisagov/cyhy_amis · branch develop · scanned 17 Jun 2026 · 418 resources

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

High 10

High Provisioned IOPS (io1/io2) Cost · 6 places

Usage of Provisioned IOPS SSD (io1/io2). These are very expensive.

How to fix

Verify if gp3 can meet performance requirements at a lower cost.

Where

High Expensive NAT Gateway Cost · 3 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 Missing AWS Budget Cost · 1 place

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

Medium 235

Medium Ensure every security group and rule has a description Security · 56 places
Medium Missing Spot Instance Usage Cost · 33 places
Medium Ensure Terraform module sources use a commit hash Security · 11 places
Medium Route53 A Record has Attached Resource Security · 10 places
Medium Ensure no NACL allow ingress from 0.0.0.0:0 to port 3389 Security · 10 places
Medium Ensure Terraform module sources use a tag with a version number Security · 10 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 8 places
Medium Ensure that EC2 is EBS optimized Security · 8 places
Medium Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK) Security · 8 places
Medium Ensure block is handling task errors properly Security · 7 places
Medium Ensure top-level permissions are not set to write-all Security · 5 places
Medium Ensure NACL ingress does not allow all Ports Security · 5 places
Medium CloudWatch Logs Without Retention Cost · 4 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 the default security group of every VPC restricts all traffic Security · 3 places

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 3 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 3 places
Medium Ensure all data stored in the SNS topic is encrypted Security · 3 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 3 places
Medium Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances Security · 2 places

Ensure that all EIP addresses allocated to a VPC are attached to EC2 instances

Documentation

Where

Medium Ensure an IAM role is attached to EC2 instance Security · 2 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 2 places

Ensure that an S3 bucket has a lifecycle configuration

Documentation

Where

Medium Ensure S3 buckets should have event notifications enabled Security · 2 places

Ensure S3 buckets should have event notifications enabled

Documentation

Where

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 2 places

Ensure that AWS Lambda function is configured for function-level concurrent execution limit

Documentation

Where

Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 2 places

Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)

Documentation

Where

Medium Ensure that S3 bucket has cross-region replication enabled Security · 2 places

Ensure that S3 bucket has cross-region replication enabled

Documentation

Where

Medium Ensure that S3 buckets are encrypted with KMS by default Security · 2 places

Ensure that S3 buckets are encrypted with KMS by default

Documentation

Where

Medium Ensure the S3 bucket has access logging enabled Security · 2 places

Ensure the S3 bucket has access logging enabled

Documentation

Where

Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 2 places

Ensure all data stored in the S3 bucket have versioning enabled

Documentation

Where

Medium Ensure no NACL allow ingress from 0.0.0.0:0 to port 22 Security · 2 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 2 places

Ensure AWS Lambda function is configured to validate code-signing

Documentation

Where

Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 2 places

Ensure access is controlled through SSO and not AWS IAM defined users

Documentation

Where

Medium Ensure Lambda Runtime is not deprecated Security · 2 places
Medium Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.) Security · 2 places

Ensure IAM policies are attached only to groups or roles (Reducing access management complexity may in-turn reduce opportunity for a principal to inadvertently receive or retain excessive privileges.)

Documentation

Where

Medium X-Ray tracing is enabled for Lambda Security · 2 places
Medium EC2 instance should not have public IP. Security · 2 places
Medium Missing S3 Lifecycle Policy Cost · 2 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 IAM policies does not allow write access without constraints Security · 1 place

Ensure IAM policies does not allow write access without constraints

Documentation

Where

Medium Check encryption settings for Lambda environmental variable Security · 1 place

Check encryption settings for Lambda environmental variable

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

and 5 more groups with 5 findings

Low 7

Low Unassociated Elastic IP Cost · 4 places

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 Cost · 3 places

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.