InfraScan Cloud

Repository scan

GCGS-Central-Digital-Platform

cabinetoffice/GCGS-Central-Digital-Platform · branch main · scanned 25 Jun 2026 · 593 resources

DOverall
FSecurity
–Reliability · N/A
CCost
1,489findings · 0 critical, 336 high
$4,271–$4,338estimated savings per month, from the code

High 835

High 246 known vulnerabilities in unknown@unknown (postgres:16.3) Security · 246 CVEs

How to fix

No fixed version of unknown is available yet. Check whether postgres:16.3 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-5222 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-2025-6965 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2026-48962 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-27664 fixed in no fix yet
  • High CVE-2022-2879 fixed in no fix yet
  • High CVE-2022-2880 fixed in no fix yet
  • High CVE-2022-29804 fixed in no fix yet
  • High CVE-2022-30631 fixed in no fix yet
  • High CVE-2022-30633 fixed in no fix yet
  • High CVE-2022-41715 fixed in no fix yet
  • High CVE-2022-41716 fixed in no fix yet
  • High CVE-2022-41720 fixed in no fix yet
  • High CVE-2022-41722 fixed in no fix yet
  • and 226 more
High 197 known vulnerabilities in unknown@unknown (redis:7.4.1) Security · 197 CVEs

How to fix

No fixed version of unknown is available yet. Check whether redis:7.4.1 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-42010 fixed in no fix yet
  • High CVE-2026-42012 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2026-48962 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-27664 fixed in no fix yet
  • High CVE-2022-2879 fixed in no fix yet
  • High CVE-2022-2880 fixed in no fix yet
  • High CVE-2022-29804 fixed in no fix yet
  • High CVE-2022-30631 fixed in no fix yet
  • High CVE-2022-30633 fixed in no fix yet
  • High CVE-2022-41715 fixed in no fix yet
  • High CVE-2022-41716 fixed in no fix yet
  • High CVE-2022-41720 fixed in no fix yet
  • High CVE-2022-41722 fixed in no fix yet
  • High CVE-2022-41723 fixed in no fix yet
  • High CVE-2022-41724 fixed in no fix yet
  • High CVE-2022-41725 fixed in no fix yet
  • and 177 more
High 193 known vulnerabilities in unknown@unknown (nginx:1.27) Security · 193 CVEs

How to fix

No fixed version of unknown is available yet. Check whether nginx:1.27 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-5222 fixed in no fix yet
  • High CVE-2025-64720 fixed in no fix yet
  • High CVE-2025-65018 fixed in no fix yet
  • High CVE-2025-66293 fixed in no fix yet
  • High CVE-2026-32741 fixed in no fix yet
  • High CVE-2026-32882 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-48962 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-2023-52425 fixed in no fix yet
  • High CVE-2024-25062 fixed in no fix yet
  • High CVE-2024-8176 fixed in no fix yet
  • High CVE-2025-15281 fixed in no fix yet
  • High CVE-2025-6021 fixed in no fix yet
  • High CVE-2025-69420 fixed in no fix yet
  • High CVE-2025-69421 fixed in no fix yet
  • High CVE-2025-7424 fixed in no fix yet
  • High CVE-2025-9230 fixed in no fix yet
  • and 173 more
High 132 known vulnerabilities in unknown@unknown (mysql:5.7) Security · 132 CVEs

How to fix

No fixed version of unknown is available yet. Check whether mysql:5.7 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-2024-56171 fixed in no fix yet
  • High CVE-2024-56171 fixed in no fix yet
  • High CVE-2025-24928 fixed in no fix yet
  • High CVE-2025-24928 fixed in no fix yet
  • High CVE-2023-27561 fixed in no fix yet
  • High CVE-2023-24539 fixed in no fix yet
  • High CVE-2023-29400 fixed in no fix yet
  • High CVE-2025-31133 fixed in no fix yet
  • High CVE-2025-52565 fixed in no fix yet
  • High CVE-2025-52881 fixed in no fix yet
  • High CVE-2023-0286 fixed in no fix yet
  • High CVE-2022-27664 fixed in no fix yet
  • High CVE-2022-2879 fixed in no fix yet
  • High CVE-2022-2880 fixed in no fix yet
  • High CVE-2022-29804 fixed in no fix yet
  • High CVE-2022-30631 fixed in no fix yet
  • High CVE-2022-30633 fixed in no fix yet
  • High CVE-2022-41715 fixed in no fix yet
  • High CVE-2022-41716 fixed in no fix yet
  • High CVE-2022-41720 fixed in no fix yet
  • and 112 more
High 14 known vulnerabilities in stdlib@1.18.2 (mysql:5.7) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in mysql:5.7. 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.4); 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-2022-28131 fixed in 1.18.4
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • 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 14 known vulnerabilities in stdlib@1.18.2 (postgres:16.3) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in postgres:16.3. 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.4); 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-2022-28131 fixed in 1.18.4
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • 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 14 known vulnerabilities in stdlib@1.18.2 (redis:7.4.1) Security · 14 CVEs

How to fix

Update stdlib from 1.18.2 to 1.18.4 or later in redis:7.4.1. 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.4); 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-2022-28131 fixed in 1.18.4
  • High CVE-2022-30630 fixed in 1.18.4
  • High CVE-2022-30632 fixed in 1.18.4
  • High CVE-2022-30634 fixed in 1.18.3
  • High CVE-2022-30635 fixed in 1.18.4
  • High CVE-2022-32189 fixed in 1.18.5
  • 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 5 known vulnerabilities in libxml2@2.9.1-6.0.3.el7_9.6 (mysql:5.7) Security · 5 CVEs

How to fix

Update libxml2 from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.7.el7_9.6 or later in mysql:5.7. 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:2.9.1-6.0.7.el7_9.6); 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-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
  • Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 5 known vulnerabilities in libxml2-python@2.9.1-6.0.3.el7_9.6 (mysql:5.7) Security · 5 CVEs

How to fix

Update libxml2-python from 2.9.1-6.0.3.el7_9.6 to 0:2.9.1-6.0.7.el7_9.6 or later in mysql:5.7. 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:2.9.1-6.0.7.el7_9.6); 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-32414 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49794 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-49796 fixed in 0:2.9.1-6.0.7.el7_9.6
  • High CVE-2025-6021 fixed in 0:2.9.1-6.0.7.el7_9.6
  • Medium CVE-2025-32415 fixed in 0:2.9.1-6.0.11.el7_9.6
High 4 known vulnerabilities in python@2.7.5-94.0.1.el7_9 (mysql:5.7) Security · 4 CVEs

How to fix

Update python from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.7.el7_9 or later in mysql:5.7. 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:2.7.5-94.0.7.el7_9); 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-4519 fixed in 0:2.7.5-94.0.7.el7_9
  • Medium CVE-2025-12084 fixed in 0:2.7.5-94.0.3.el7_9
  • Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
  • Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
High 4 known vulnerabilities in python-libs@2.7.5-94.0.1.el7_9 (mysql:5.7) Security · 4 CVEs

How to fix

Update python-libs from 2.7.5-94.0.1.el7_9 to 0:2.7.5-94.0.7.el7_9 or later in mysql:5.7. 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:2.7.5-94.0.7.el7_9); 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-4519 fixed in 0:2.7.5-94.0.7.el7_9
  • Medium CVE-2025-12084 fixed in 0:2.7.5-94.0.3.el7_9
  • Medium CVE-2025-15366 fixed in 0:2.7.5-94.0.5.el7_9
  • Medium CVE-2025-15367 fixed in 0:2.7.5-94.0.5.el7_9
High 2 known vulnerabilities in krb5-libs@1.15.1-55.0.1.el7_9 (mysql:5.7) Security · 2 CVEs

How to fix

Update krb5-libs from 1.15.1-55.0.1.el7_9 to 0:1.15.1-55.0.7.el7_9 or later in mysql:5.7. 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:1.15.1-55.0.7.el7_9); 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-3596 fixed in 0:1.15.1-55.0.7.el7_9
  • Medium CVE-2025-24528 fixed in 0:1.15.1-55.0.9.el7_9
High 1 known vulnerability in gnupg2@2.0.22-5.el7_5 (mysql:5.7) Security · 1 CVE

How to fix

Update gnupg2 from 2.0.22-5.el7_5 to 0:2.0.22-5.0.1.el7_5 or later in mysql:5.7. 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:2.0.22-5.0.1.el7_5); 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-68973 fixed in 0:2.0.22-5.0.1.el7_5
High 1 known vulnerability in sqlite@3.7.17-8.el7_7.1 (mysql:5.7) Security · 1 CVE

How to fix

Update sqlite from 3.7.17-8.el7_7.1 to 0:3.7.17-8.0.1.el7_9.1 or later in mysql:5.7. 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:3.7.17-8.0.1.el7_9.1); 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-6965 fixed in 0:3.7.17-8.0.1.el7_9.1
High 1 known vulnerability in zlib@1.2.7-21.el7_9 (mysql:5.7) Security · 1 CVE

How to fix

Update zlib from 1.2.7-21.el7_9 to 0:1.2.7-21.0.1.el7_9 or later in mysql:5.7. 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:1.2.7-21.0.1.el7_9); 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-2016-9840 fixed in 0:1.2.7-21.0.1.el7_9
High EBS Provisioned IOPS (io1/io2) Cost · 1 place

EBS volume using Provisioned IOPS (io1/io2) type. These are very expensive — io2 costs 56× more than gp3 per GB plus per-IOPS charges.

How to fix

Verify if gp3 can meet performance requirements at a lower cost.

Where

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 629

Medium Ensure AWS Load Balancer doesn't use HTTP protocol Security · 117 places
Medium Ensure that CloudWatch Log Group is encrypted by KMS Security · 28 places
Medium Ensure CloudWatch log groups retains logs for at least 1 year Security · 28 places
Medium Ensure S3 buckets should have event notifications enabled Security · 26 places
Medium Ensure that S3 bucket has cross-region replication enabled Security · 26 places
Medium Ensure that an S3 bucket has a lifecycle configuration Security · 23 places
Medium Ensure that S3 buckets are encrypted with KMS by default Security · 18 places
Medium Ensure that Security Groups are attached to another resource Security · 17 places
Medium Ensure access control lists for S3 buckets are disabled Security · 16 places
Medium Ensure all data stored in the S3 bucket have versioning enabled Reliability · 13 places
Medium Ensure all data stored in the SQS queue is encrypted Security · 12 places
Medium Ensure no IAM policies documents allow "*" as a statement's resource for restrictable actions Security · 12 places
Medium Ensure that S3 bucket has a Public Access block Security · 11 places
Medium Ensure IAM policies does not allow write access without constraints Security · 10 places
Medium Ensure State Machine has X-Ray tracing enabled Security · 10 places
Medium Ensure State Machine has execution history logging enabled Security · 10 places
Medium Ensure S3 bucket has block public ACLS enabled Security · 10 places
Medium Ensure S3 bucket has block public policy enabled Security · 10 places
Medium Ensure S3 bucket has ignore public ACLs enabled Security · 10 places
Medium Ensure S3 bucket has 'restrict_public_buckets' enabled Security · 10 places
Medium Ensure DB instance gets all minor upgrades automatically Security · 9 places
Medium Ensure Secrets Manager secrets should have automatic rotation enabled Security · 8 places
Medium Ensure that Secrets Manager secret is encrypted using KMS CMK Security · 8 places
Medium Ensure RDS Performance Insights are encrypted using KMS CMKs Security · 8 places
Medium Missing Cost and Usage Report Cost · 8 places
Medium AWS SSM Parameter should be Encrypted Security · 7 places
Medium Ensure the S3 bucket has access logging enabled Security · 7 places
Medium Ensure that RDS clusters has backup plan of AWS Backup Reliability · 5 places
Medium Ensure RDS cluster has IAM authentication enabled Security · 5 places
Medium Ensure the ELBv2 (Application/Network) has access logging enabled Security · 5 places
Medium Load Balancer for Single Instance Cost · 5 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 CloudFront distribution has a response headers policy attached Security · 4 places
Medium Ensure Domain Name System Security Extensions (DNSSEC) signing is enabled for Amazon Route 53 public hosted zones Security · 4 places
Medium Ensure Domain Name System (DNS) query logging is enabled for Amazon Route 53 hosted zones Security · 4 places
Medium Ensure AWS CloudFront attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 4 places
Medium Ensure AWS ALB attached WAFv2 WebACL is configured with AMR for Log4j Vulnerability Security · 4 places

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

How to fix

See Checkov documentation for remediation guidance.

Where

Medium Ensure WAF prevents message lookup in Log4j2. See CVE-2021-44228 aka log4jshell Security · 4 places
Medium Ensure that RDS Cluster log capture is enabled Security · 4 places
Medium Ensure Postgres RDS as aws_rds_cluster has Query Logging enabled Security · 3 places
Medium Ensure AWS API gateway request is validated Security · 3 places

and 75 more groups with 103 findings

Low 25

Low Missing AWS Budget Cost · 8 places
Low SQS Max Message Retention Cost · 7 places

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

Low 2 known vulnerabilities in tiff@4.5.0-6%2Bdeb12u2 (nginx:1.27) Security · 2 CVEs

How to fix

No fixed version of tiff is available yet. Check whether nginx:1.27 needs tiff 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-2018-10126 fixed in no fix yet
  • Low CVE-2024-6716 fixed in no fix yet
Low 1 known vulnerability in sys@0.0.0-20220907062415-87db552b00fd (mysql:5.7) Security · 1 CVE

How to fix

Update sys from 0.0.0-20220907062415-87db552b00fd to 0.44.0 or later in mysql:5.7. 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.44.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

  • Low CVE-2026-39824 fixed in 0.44.0
Low 1 known vulnerability in gcc-12@12.2.0-14%2Bdeb12u1 (nginx:1.27) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether nginx:1.27 needs gcc-12 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-2022-27943 fixed in no fix yet
Low 1 known vulnerability in perl@5.36.0-7%2Bdeb12u2 (nginx:1.27) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether nginx:1.27 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 1 known vulnerability in gcc-12@12.2.0-14 (postgres:16.3) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether postgres:16.3 needs gcc-12 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-2022-27943 fixed in no fix yet
Low 1 known vulnerability in perl@5.36.0-7%2Bdeb12u1 (postgres:16.3) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether postgres:16.3 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 1 known vulnerability in gcc-12@12.2.0-14 (redis:7.4.1) Security · 1 CVE

How to fix

No fixed version of gcc-12 is available yet. Check whether redis:7.4.1 needs gcc-12 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-2022-27943 fixed in no fix yet
Low 1 known vulnerability in perl@5.36.0-7%2Bdeb12u1 (redis:7.4.1) Security · 1 CVE

How to fix

No fixed version of perl is available yet. Check whether redis:7.4.1 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

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.