InfraScan Cloud

Repository scan

secure-cloud-architecture

UniteLiveDisperseDie/secure-cloud-architecture · branch main · scanned 25 Jun 2026 · 604 resources

DOverall
DSecurity
–Reliability · N/A
CCost
242findings · 0 critical, 2 high
$45.21–$126estimated savings per month, from the code

High 2

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

Medium 228

Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 13 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 11 places
Medium Missing Cost and Usage Report Cost · 11 places
Medium Ensure IAM policies does not allow write access without constraints Security · 9 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 9 places
Medium Ensure S3 buckets should have event notifications enabled Security · 8 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 8 places
Medium Ensure the S3 bucket has access logging enabled Security · 8 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 7 places
Medium Disallow IAM roles, users, and groups from using the AWS AdministratorAccess policy Security · 7 places
Medium Ensure that Security Groups are attached to another resource Security · 6 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 6 places
Medium Ensure IAM policies does not allow credentials exposure Security · 5 places
Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 5 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 4 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 4 places
Medium Ensure all data stored in the SNS topic is encrypted Security · 4 places
Medium Ensure the default security group of every VPC restricts all traffic Security · 3 places
Medium Ensure public facing ALB are protected by WAF Security · 3 places
Medium Ensure WAF2 has a Logging Configuration Security · 3 places
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 3 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 3 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 3 places
Medium Check encryption settings for Lambda environmental variable Security · 3 places
Medium Ensure CloudTrail defines an SNS Topic Security · 3 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 3 places
Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 3 places
Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 3 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 · 3 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 · 3 places
Medium Load Balancer for Single Instance Cost · 3 places

Load balancer detected. Verify it's needed - load balancers cost $15-20/month even if unused.

How to fix

Consider if load balancer is necessary for single-instance deployments or low-traffic applications.

Where

Medium Ensure VPC flow logging is enabled in all VPCs Security · 2 places
Medium Ensure CloudFront distribution has a response headers policy attached Security · 2 places
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 2 places

Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability

Documentation

Where

Medium Ensure that enhanced monitoring is enabled for Amazon RDS instances Security · 2 places
Medium Ensure VPC subnets do not assign public IP by default Security · 2 places
Medium Ensure that Load Balancer has deletion protection enabled Reliability · 2 places
Medium Ensure WAF prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell Security · 2 places

Ensure WAF prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell

Documentation

Where

Medium Ensure no NACL allow ingress from 0.0.0.0:0 to port 3389 Security · 2 places
Medium Ensure Kinesis Firehose delivery stream is encrypted Security · 2 places

and 37 more groups with 43 findings

Low 12

Low Missing AWS Budget Cost · 11 places
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 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.