InfraScan Cloud

Repository scan

viya4-iac-aws

sassoftware/viya4-iac-aws · branch main · scanned 26 Feb 2026 · 62 resources

COverall
CSecurity
–Reliability · N/A
CCost
33findings · 0 critical, 3 high
—no cost findings with a savings estimate

High 3

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

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

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 28

Medium Ensure Terraform module sources use a commit hash Security · 4 places
Medium Ensure that Security Groups are attached to another resource Security · 3 places

Ensure that Security Groups are attached to another resource

Documentation

Where

Medium Missing Spot Instance Usage Cost · 3 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 an IAM role is attached to EC2 instance Security · 2 places

Ensure an IAM role is attached to EC2 instance

Documentation

Where

Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 2 places

Ensure that detailed monitoring is enabled for EC2 instances

Documentation

Where

Medium Ensure that EC2 is EBS optimized Security · 2 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 2 places

Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions

Documentation

Where

Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 2 places

Ensure Instance Metadata Service Version 1 is not enabled

Documentation

Where

Medium Ensure VPC flow logging is enabled in all VPCs Security · 1 place

Ensure VPC flow logging is enabled in all VPCs

Documentation

Where

Medium Ensure the default security group of every VPC restricts all traffic Security · 1 place

Ensure the default security group of every VPC restricts all traffic

Documentation

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 Ensure VPC subnets do not assign public IP by default Security · 1 place

Ensure VPC subnets do not assign public IP by default

Documentation

Where

Medium Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure EBS Volume is encrypted by KMS using a customer managed Key (CMK)

Documentation

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 Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 1 place

Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions

Documentation

Where

Medium Missing Cost and Usage Report Cost · 1 place

No AWS Cost and Usage Report (CUR) configured. CUR provides detailed cost tracking and analysis.

How to fix

Enable AWS Cost and Usage Reports to track spending patterns and identify optimization opportunities.

Where

Low 2

Low Elastic IP Usage Cost · 2 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

Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 26 Feb 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.