Repository scan
BloodConnect
CraftsmenLtd/BloodConnect · branch main · scanned 25 Jun 2026 · 105 resources
Medium 49
Medium Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Ensure that AWS Lambda function is configured for function-level concurrent execution limit
Where
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
Medium Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Ensure that AWS Lambda function is configured for a Dead Letter Queue(DLQ)
Where
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
Medium Ensure that AWS Lambda function is configured inside a VPC
Ensure that AWS Lambda function is configured inside a VPC
Where
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
Medium Ensure AWS Lambda function is configured to validate code-signing
Ensure AWS Lambda function is configured to validate code-signing
Where
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
Medium X-Ray tracing is enabled for Lambda
X-Ray tracing is enabled for Lambda
Where
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
- ../../iac/terraform/aws/lambda/lambda.tf:7
Medium Missing Cost and Usage Report
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
Ensure AWS CloudFront web distribution has geo restriction enabled
Where
Medium API Gateway REST Instead of HTTP API
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
- iac/terraform/aws/api_gw.tf:1 $2.50 / mo
Low 1
Low SQS Max Message Retention
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.