InfraScan Cloud

Repository scan

spot-checker

ddps-lab/spot-checker · branch main · scanned 25 Jun 2026 · 184 resources

DOverall
DSecurity
–Reliability · N/A
CCost
233findings · 0 critical, 0 high
$8.62estimated savings per month, from the code

Medium 221

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 20 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 20 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 15 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 15 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 15 places
Medium Check encryption settings for Lambda environmental variable Security · 15 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 15 places
Medium X-Ray tracing is enabled for Lambda Security · 15 places
Medium Missing Cost and Usage Report Cost · 10 places
Medium Ensure that S3 bucket has a Public Access block Security · 6 places
Medium Ensure S3 buckets should have event notifications enabled Security · 6 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 6 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 6 places
Medium Ensure the S3 bucket has access logging enabled Security · 6 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 6 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 5 places
Medium Ensure every security group and rule has a description Security · 4 places
Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 22 Security · 4 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 VPC flow logging is enabled in all VPCs Security · 2 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 2 places

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure that Security Groups are attached to another resource Security · 2 places
Medium Ensure no open CORS policy Security · 2 places
Medium Ensure that detailed monitoring is enabled for EC2 instances Security · 2 places
Medium Ensure VPC subnets do not assign public IP by default Security · 2 places
Medium Ensure that EC2 is EBS optimized Security · 2 places
Medium Ensure that Lambda function URLs AuthType is not None Security · 2 places
Medium Disallow IAM roles, users, and groups from using the AWS AdministratorAccess policy Security · 2 places

Disallow IAM roles, users, and groups from using the AWS AdministratorAccess policy

Documentation

Where

Medium Ensure Instance Metadata Service Version 1 is not enabled Security · 2 places
Medium Lambda Over-Provisioned Memory Cost · 2 places

Lambda function with memory >= 3008 MB (the old Lambda maximum, a common cargo-cult setting). Lambda pricing scales linearly with memory; over-provisioning directly inflates costs.

How to fix

Profile the function with AWS Lambda Power Tuning and reduce memory to the minimum needed. Most functions run fine at 256–1024 MB.

Where

Medium Ensure S3 lifecycle configuration sets period for aborting failed uploads Security · 1 place

Ensure S3 lifecycle configuration sets period for aborting failed uploads

Documentation

Where

Medium Ensure 'Block Project-wide SSH keys' is enabled for VM instances Security · 1 place

Ensure 'Block Project-wide SSH keys' is enabled for VM instances

Documentation

Where

Medium Ensure Compute instances are launched with Shielded VM enabled Security · 1 place

Ensure Compute instances are launched with Shielded VM enabled

Documentation

Where

Medium Ensure that Compute instances do not have public IP addresses Security · 1 place

Ensure that Compute instances do not have public IP addresses

Documentation

Where

Low 12

Low Missing AWS Budget Cost · 10 places
Low Large Root Volume Cost · 2 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 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.