InfraScan Cloud

Repository scan

BloodConnect

CraftsmenLtd/BloodConnect · branch main · scanned 25 Jun 2026 · 105 resources

COverall
CSecurity
–Reliability · N/A
BCost
50findings · 0 critical, 0 high
$2.50estimated savings per month, from the code

Medium 49

Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit Security · 9 places
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ) Security · 9 places
Medium Ensure that AWS Lambda function is configured inside a VPC Security · 9 places
Medium Ensure AWS Lambda function is configured to validate code-signing Security · 9 places
Medium X-Ray tracing is enabled for Lambda Security · 9 places
Medium Missing Cost and Usage Report Cost · 2 places

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

Medium Ensure AWS CloudFront web distribution has geo restriction enabled Security · 1 place

Ensure AWS CloudFront web distribution has geo restriction enabled

Documentation

Where

Medium API Gateway REST Instead of HTTP API Cost · 1 place

aws_api_gateway_rest_api (REST API) costs ~3.5x more per million requests than aws_apigatewayv2_api (HTTP API). Most modern use cases are supported by the HTTP API.

How to fix

Migrate to aws_apigatewayv2_api (HTTP API v2) unless REST-specific features (usage plans, request validation, custom authorizers v1) are required.

Where

Low 1

Low SQS Max Message Retention Cost · 1 place

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

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.