InfraScan Cloud

Repository scan

cloudOps-backend

Badreddiine/cloudOps-backend · branch main · scanned 25 Jun 2026 · 95 resources

DOverall
FSecurity
–Reliability · N/A
BCost
603findings · 0 critical, 214 high
$3.65–$37.85estimated savings per month, from the code

High 520

High 244 known vulnerabilities in unknown@unknown (grafana/promtail:2.9.4) Security · 244 CVEs

How to fix

No fixed version of unknown is available yet. Check whether grafana/promtail:2.9.4 needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2023-47038 fixed in no fix yet
  • High CVE-2025-24528 fixed in no fix yet
  • High CVE-2026-42010 fixed in no fix yet
  • High CVE-2026-42012 fixed in no fix yet
  • High CVE-2026-41567 fixed in no fix yet
  • High CVE-2026-42306 fixed in no fix yet
  • High CVE-2024-2961 fixed in no fix yet
  • High CVE-2024-33601 fixed in no fix yet
  • High CVE-2026-48962 fixed in no fix yet
  • High CVE-2024-33602 fixed in no fix yet
  • High CVE-2025-69419 fixed in no fix yet
  • High CVE-2026-42011 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45283 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2023-50387 fixed in no fix yet
  • High CVE-2023-50868 fixed in no fix yet
  • High CVE-2024-0553 fixed in no fix yet
  • High CVE-2024-0567 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • and 224 more
High 93 known vulnerabilities in unknown@unknown (grafana/loki:2.9.4) Security · 93 CVEs

How to fix

No fixed version of unknown is available yet. Check whether grafana/loki:2.9.4 needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45283 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-22868 fixed in no fix yet
  • High CVE-2025-22869 fixed in no fix yet
  • High CVE-2025-58187 fixed in no fix yet
  • High CVE-2025-58188 fixed in no fix yet
  • High CVE-2025-61723 fixed in no fix yet
  • High CVE-2025-61725 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61729 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-32285 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • and 73 more
High 90 known vulnerabilities in unknown@unknown (jaegertracing/all-in-one:1.52) Security · 90 CVEs

How to fix

No fixed version of unknown is available yet. Check whether jaegertracing/all-in-one:1.52 needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2026-24051 fixed in no fix yet
  • High CVE-2026-39883 fixed in no fix yet
  • High CVE-2022-30635 fixed in no fix yet
  • High CVE-2023-45283 fixed in no fix yet
  • High CVE-2023-45288 fixed in no fix yet
  • High CVE-2024-24784 fixed in no fix yet
  • High CVE-2024-24791 fixed in no fix yet
  • High CVE-2024-34156 fixed in no fix yet
  • High CVE-2025-22869 fixed in no fix yet
  • High CVE-2025-58187 fixed in no fix yet
  • High CVE-2025-58188 fixed in no fix yet
  • High CVE-2025-61723 fixed in no fix yet
  • High CVE-2025-61725 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61729 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • and 70 more
High 31 known vulnerabilities in unknown@unknown (postgres:15-alpine) Security · 31 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:15-alpine needs unknown at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2025-58187 fixed in no fix yet
  • High CVE-2025-58188 fixed in no fix yet
  • High CVE-2025-61723 fixed in no fix yet
  • High CVE-2025-61725 fixed in no fix yet
  • High CVE-2025-61726 fixed in no fix yet
  • High CVE-2025-61729 fixed in no fix yet
  • High CVE-2026-32280 fixed in no fix yet
  • High CVE-2026-32281 fixed in no fix yet
  • High CVE-2026-32283 fixed in no fix yet
  • High CVE-2026-33814 fixed in no fix yet
  • High CVE-2026-39820 fixed in no fix yet
  • High CVE-2025-68121 fixed in no fix yet
  • Medium CVE-2025-58183 fixed in no fix yet
  • Medium CVE-2025-47912 fixed in no fix yet
  • Medium CVE-2025-58186 fixed in no fix yet
  • Medium CVE-2025-58189 fixed in no fix yet
  • Medium CVE-2025-61724 fixed in no fix yet
  • Medium CVE-2025-61730 fixed in no fix yet
  • Medium CVE-2026-39825 fixed in no fix yet
  • Medium CVE-2026-42507 fixed in no fix yet
  • and 11 more
High 10 known vulnerabilities in openssl@3.1.4-r1 (grafana/loki:2.9.4) Security · 10 CVEs

How to fix

Update openssl from 3.1.4-r1 to 3.1.6-r0 or later in grafana/loki:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1.6-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-4741 fixed in 3.1.6-r0
  • High CVE-2024-6119 fixed in 3.1.7-r0
  • High CVE-2024-5535 fixed in 3.1.6-r0
  • Medium CVE-2024-13176 fixed in 3.1.8-r0
  • Medium CVE-2024-9143 fixed in 3.1.7-r1
  • Medium CVE-2024-4603 fixed in 3.1.5-r0
  • Medium CVE-2024-0727 fixed in 3.1.4-r5
  • Medium CVE-2023-6237 fixed in 3.1.4-r4
  • Medium CVE-2024-2511 fixed in 3.1.4-r6
  • Medium CVE-2023-6129 fixed in 3.1.4-r3
High 8 known vulnerabilities in stdlib@1.21.3 (grafana/loki:2.9.4) Security · 8 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/loki:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.22.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 8 known vulnerabilities in stdlib@1.21.3 (grafana/promtail:2.9.4) Security · 8 CVEs

How to fix

Update stdlib from 1.21.3 to 1.22.7 or later in grafana/promtail:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.22.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 8 known vulnerabilities in stdlib@1.21.4 (jaegertracing/all-in-one:1.52) Security · 8 CVEs

How to fix

Update stdlib from 1.21.4 to 1.22.7 or later in jaegertracing/all-in-one:1.52. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.22.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-34158 fixed in 1.22.7
  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
  • Medium CVE-2025-4673 fixed in 1.23.10
High 6 known vulnerabilities in stdlib@1.24.6 (postgres:15-alpine) Security · 6 CVEs

How to fix

Update stdlib from 1.24.6 to 1.25.8 or later in postgres:15-alpine. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.25.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-25679 fixed in 1.25.8
  • High CVE-2026-33811 fixed in 1.25.10
  • High CVE-2026-39836 fixed in 1.25.10
  • High CVE-2026-42499 fixed in 1.25.10
  • High CVE-2026-42504 fixed in 1.25.11
  • Medium CVE-2025-58185 fixed in 1.24.8
High 4 known vulnerabilities in crypto@0.18.0 (grafana/loki:2.9.4) Security · 4 CVEs

How to fix

Update crypto from 0.18.0 to 0.43.0 or later in grafana/loki:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.43.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
High 4 known vulnerabilities in crypto@0.18.0 (grafana/promtail:2.9.4) Security · 4 CVEs

How to fix

Update crypto from 0.18.0 to 0.43.0 or later in grafana/promtail:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.43.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
High 4 known vulnerabilities in crypto@0.16.0 (jaegertracing/all-in-one:1.52) Security · 4 CVEs

How to fix

Update crypto from 0.16.0 to 0.43.0 or later in jaegertracing/all-in-one:1.52. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.43.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-47913 fixed in 0.43.0
  • High CVE-2026-46597 fixed in 0.52.0
  • High CVE-2026-42508 fixed in 0.52.0
  • Medium CVE-2026-46598 fixed in 0.52.0
High 3 known vulnerabilities in net@0.17.0 (grafana/loki:2.9.4) Security · 3 CVEs

How to fix

Update net from 0.17.0 to 0.53.0 or later in grafana/loki:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.53.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33814 fixed in 0.53.0
  • Medium CVE-2025-22870 fixed in 0.36.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 2 known vulnerabilities in net@0.19.0 (jaegertracing/all-in-one:1.52) Security · 2 CVEs

How to fix

Update net from 0.19.0 to 0.53.0 or later in jaegertracing/all-in-one:1.52. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.53.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2026-33814 fixed in 0.53.0
  • Medium CVE-2026-25680 fixed in 0.55.0
High 1 known vulnerability in musl@1.2.4-r2 (grafana/loki:2.9.4) Security · 1 CVE

How to fix

Update musl from 1.2.4-r2 to 1.2.4-r3 or later in grafana/loki:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.4-r3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-26519 fixed in 1.2.4-r3
High 1 known vulnerability in e2scrub@.service (grafana/promtail:2.9.4) Security · 1 CVE

How to fix

No fixed version of e2scrub is available yet. Check whether grafana/promtail:2.9.4 needs e2scrub at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • High CVE-2022-1304 fixed in no fix yet
High 1 known vulnerability in krb5@1.18.3-6%2Bdeb11u4 (grafana/promtail:2.9.4) Security · 1 CVE

How to fix

Update krb5 from 1.18.3-6%2Bdeb11u4 to 1.18.3-6+deb11u5 or later in grafana/promtail:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.18.3-6+deb11u5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2024-37371 fixed in 1.18.3-6+deb11u5
High 1 known vulnerability in musl@1.2.3-r3 (jaegertracing/all-in-one:1.52) Security · 1 CVE

How to fix

Update musl from 1.2.3-r3 to 1.2.3-r4 or later in jaegertracing/all-in-one:1.52. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.3-r4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • High CVE-2025-26519 fixed in 1.2.3-r4
High Expensive NAT Gateway Cost · 1 place

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 78

Medium Base64 High Entropy String Security · 7 places
Medium Ensure that Security Groups are attached to another resource Security · 6 places
Medium Ensure every security group and rule has a description Security · 6 places
Medium Ensure top-level permissions are not set to write-all Security · 5 places
Medium 4 known vulnerabilities in busybox@1.36.1-r5 (grafana/loki:2.9.4) Security · 4 CVEs

How to fix

Update busybox from 1.36.1-r5 to 1.36.1-r7 or later in grafana/loki:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.36.1-r7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-42363 fixed in 1.36.1-r7
  • Medium CVE-2023-42364 fixed in 1.36.1-r7
  • Medium CVE-2023-42365 fixed in 1.36.1-r7
  • Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 4 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 4 places
Medium Ensure that HEALTHCHECK instructions have been added to container images Security · 4 places
Medium Ensure VPC subnets do not assign public IP by default Security · 3 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 3 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 3 places
Medium Ensure RDS instance with copy tags to snapshots is enabled Security · 2 places

Ensure RDS instance with copy tags to snapshots is enabled

Documentation

Where

Medium Ensure AWS RDS database instance configured with encryption in transit Security · 2 places

Ensure AWS RDS database instance configured with encryption in transit

Documentation

Where

Medium Ensure RDS database has IAM authentication enabled Security · 2 places

Ensure RDS database has IAM authentication enabled

Documentation

Where

Medium Ensure DB instance gets all minor upgrades automatically Security · 2 places

Ensure DB instance gets all minor upgrades automatically

Documentation

Where

Medium Ensure that AWS database instances have deletion protection enabled Reliability · 2 places

Ensure that AWS database instances have deletion protection enabled

Documentation

Where

Medium Ensure RDS Performance Insights are encrypted using KMS CMKs Security · 2 places

Ensure RDS Performance Insights are encrypted using KMS CMKs

Documentation

Where

Medium Ensure no security groups allow egress from 0.0.0.0:0 to port -1 Security · 2 places
Medium 1 known vulnerability in bc-fips@2.1.2 (bitnami/jmx-exporter:latest) Security · 1 CVE

How to fix

No fixed version of bc-fips is available yet. Check whether bitnami/jmx-exporter:latest needs bc-fips at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2026-8149 fixed in no fix yet
Medium 1 known vulnerability in net@0.17.0 (grafana/promtail:2.9.4) Security · 1 CVE

How to fix

Update net from 0.17.0 to 0.55.0 or later in grafana/promtail:2.9.4. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.55.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2026-25680 fixed in 0.55.0
Medium 1 known vulnerability in busybox@1.35.0-r17 (jaegertracing/all-in-one:1.52) Security · 1 CVE

How to fix

Update busybox from 1.35.0-r17 to 1.35.0-r18 or later in jaegertracing/all-in-one:1.52. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.35.0-r18); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.

Vulnerabilities

  • Medium CVE-2023-42366 fixed in 1.35.0-r18
Medium 1 known vulnerability in busybox@1.37.0-r14 (redis:7-alpine) Security · 1 CVE

How to fix

No fixed version of busybox is available yet. Check whether redis:7-alpine needs busybox at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2025-60876 fixed in no fix yet
Medium 1 known vulnerability in util-linux@2.40.4-r1 (redis:7-alpine) Security · 1 CVE

How to fix

No fixed version of util-linux is available yet. Check whether redis:7-alpine needs util-linux at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Medium CVE-2026-27456 fixed in no fix yet
Medium Ensure the default security group of every VPC restricts all traffic Security · 1 place

Ensure the default security group of every VPC restricts all traffic

Documentation

Where

Medium Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK) Security · 1 place

Ensure ElastiCache replication group is encrypted by KMS using a customer managed Key (CMK)

Documentation

Where

Medium Ensure no security groups allow ingress from 0.0.0.0:0 to port 80 Security · 1 place

Ensure no security groups allow ingress from 0.0.0.0:0 to port 80

Documentation

Where

Medium Ensure IAM policies does not allow write access without constraints Security · 1 place

Ensure IAM policies does not allow write access without constraints

Documentation

Where

Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit Security · 1 place

Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit

Documentation

Where

Medium Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token Security · 1 place

Ensure all data stored in the ElastiCache Replication Group is securely encrypted at transit and has auth token

Documentation

Where

Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 1 place

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

Documentation

Where

Medium Ensure MSK Cluster encryption in rest and transit is enabled Security · 1 place

Ensure MSK Cluster encryption in rest and transit is enabled

Documentation

Where

Medium Ensure that a user for the container has been created Security · 1 place

Ensure that a user for the container has been created

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 5

Low 1 known vulnerability in pcre3@2%3A8.39-13 (grafana/promtail:2.9.4) Security · 1 CVE

How to fix

No fixed version of pcre3 is available yet. Check whether grafana/promtail:2.9.4 needs pcre3 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2017-11164 fixed in no fix yet
Low 1 known vulnerability in perl@5.32.1-4%2Bdeb11u2 (grafana/promtail:2.9.4) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether grafana/promtail:2.9.4 needs perl at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.

Vulnerabilities

  • Low CVE-2011-4116 fixed in no fix yet
Low Unassociated Elastic IP Cost · 1 place

Elastic IPs are charged if not attached to a running instance or if you have more than one per instance.

How to fix

Release unattached Elastic IPs.

Where

Low Missing AWS Budget Cost · 1 place

No AWS budget configured. Budgets help monitor and control spending with alerts.

How to fix

Create AWS budgets with alerts for forecasted and actual costs to avoid unexpected charges.

Where

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.