InfraScan Cloud

Repository scan

Magento-2-aws-cluster-terraform

magenx/Magento-2-aws-cluster-terraform · branch main · scanned 27 Feb 2026 · 36 resources

DOverall
FSecurity
–Reliability · N/A
BCost
53findings · 0 critical, 0 high
—no cost findings with a savings estimate

Medium 52

Medium Ensure Terraform module sources use a commit hash Security · 26 places
Medium AWS SSM Parameter should be Encrypted Security · 7 places
Medium Missing Spot Instance Usage Cost · 4 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 Terraform module sources use a tag with a version number Security · 3 places

Ensure Terraform module sources use a tag with a version number

Documentation

Where

Medium Ensure IAM policies does not allow write access without constraints Security · 2 places

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 · 2 places

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

Documentation

Where

Medium Ensure WAF2 has a Logging Configuration Security · 1 place

Ensure WAF2 has a Logging Configuration

Documentation

Where

Medium Ensure WAF prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell Security · 1 place

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

Documentation

Where

Medium Ensure MQ broker encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure MQ broker encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure access is controlled through SSO and not AWS IAM defined users Security · 1 place

Ensure access is controlled through SSO and not AWS IAM defined users

Documentation

Where

Medium Ensure no IAM policies documents allow ALL or any AWS principal permissions to the resource Security · 1 place

Ensure no IAM policies documents allow ALL or any AWS principal permissions to the resource

Documentation

Where

Medium Ensure IAM policies does not allow permissions management / resource exposure without constraints Security · 1 place

Ensure IAM policies does not allow permissions management / resource exposure without constraints

Documentation

Where

Medium Ensure CodeBuild project environments do not have privileged mode enabled Security · 1 place

Ensure CodeBuild project environments do not have privileged mode enabled

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 1

Low EC2 Detailed Monitoring Cost · 1 place

Detailed monitoring for EC2 instances incurs extra costs.

How to fix

Disable detailed monitoring if standard 5-minute metrics are sufficient.

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 27 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.