PAGES
← all tools
◆ Reconnaissance & OSINT

cloudlist

v1.5.0 open-source

Cloudlist is a multi-cloud tool for getting assets from cloud providers, maintaining a centralized list across multiple clouds with minimal configuration.

Summary

cloudlist is an open-source command-line tool that pulls asset inventories — IPs, hostnames, services — from multiple cloud provider accounts into one centralized list. It is built for blue teams running attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. management programs who need visibility across accounts without maintaining per-provider scripts, and it works with keyless authentication schemes like AWS IRSAIRSAAn AWS mechanism that lets a Kubernetes pod assume an IAM role via a service account, so tools running in EKS can call AWS APIs without embedding long-lived credentials. and GCP workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. so it can run in existing pipelines rather than requiring stored credentials. Configuration is deliberately light: providers are defined once, output can be filtered and formatted in several ways, and results print to stdout so cloudlist chains into other reconnaissance tools rather than acting as a standalone platform. Its extensible provider model makes adding new clouds straightforward. First committed in 2020, it has 37 contributors and a dozen releases in the past year, the most recent about six months old.

Cloudlist is a multi-cloud tool for getting assets from cloud providers, maintaining a centralized list across multiple clouds with minimal configuration.

How cloudlist helps

Which assets in my cloud accounts are actually exposed as IPs and hostnames right now?

queries each configured provider's API directly and prints the current inventory, so the list reflects what exists today rather than a scan someone ran last quarter

Which cloud assets are invisible because they sit outside my main account?

pulls from every provider configured in one run and merges the results into a single list, so accounts nobody remembers to check still show up

Have I missed any assets by only scanning the providers I remember to script for?

ships provider integrations for the major clouds out of the box, so coverage doesn't depend on someone maintaining a one-off script per provider

Can I pull this inventory into my pipeline without stashing cloud credentials in it?

authenticates using each provider's native keyless scheme, such as AWS IRSA or GCP workload identity, so the pipeline's existing identity is enough

How do I get this asset list into the rest of my recon toolchain?

writes results to standard output in a choice of formats, so another tool can consume the list directly instead of parsing a report file

Which subset of my assets matches a particular service, region, or tag?

applies filters at query time so the printed list is narrowed to what's relevant before it ever reaches the next tool

all 10 features, with the evidence for each →

Languages

Not documented

Features

10 capabilities · 2 backed by code, an API document or a real run

Built from cloudlist's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • cloudlist covers 2 of the 13 network discovery and scanning capabilities we track.

What cloudlist offers you

  • Command-line interface4
All capabilities 10 capabilities
Cloud provider asset discovery verified Enumerates assets across cloud providers, with an option to retrieve extended metadata for each provider. 35 releases · 2 other sources · first seen Feb 2022

Shared capability: Attack surface inventory

release 35 total

  • Adds GCP project exclusion, allowing specific project_ids to be skipped during org-level discovery. v1.5.0 · Oct 2026 · source · release history
  • Adds new enumerated asset types across providers: AWS Elastic IPs, RDS endpoints, and ElastiCache endpoints; Azure Service Fabric clusters and managed database endpoints; GCP addresses and forwarding rules; Hetzner load balancers, floating IPs, and primary IPs; Scaleway flexible IPs, load balancers, serverless… v1.5.0 · Oct 2026 · source · release history
  • Adds AWS org discovery with account exclusion support, enabling enumeration across all accounts in an AWS Organization. v1.5.0 · Oct 2026 · source · release history
  • Adds -auto-discovery flag to automatically detect and enumerate AWS, GCP, Azure, and Kubernetes using ambient environment credentials — no provider config file required.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v1.5.0 · Oct 2026 · source · release history
  • Adds exclude_services filter (-es / -exclude-service) to skip specific services for a provider during enumeration. v1.5.0 · Oct 2026 · source · release history
  • Adds record_content to DNS metadata by @dwisiswant0 in https://github.com/projectdiscovery/cloudlist/pull/729 v1.4.0 · Feb 2026 · source · release history

command line

  • --extended-metadata — enable extended metadata for providers v1.3.0 · Jan 2026 · command-line history

example

  • Scan AWS assets but skip RDS and ElastiCache endpoints to reduce noise when you only care about compute and network exposure. cloudlist -pc ~/.config/cloudlist/provider-config.yaml -p aws -es rds,elasticache v1.5.0 · Oct 2026 · source
Short-lived credential authentication shipped Supports short-lived credentials for authenticating with cloud providers, specifically GCP. 5 releases · first seen Aug 2024

Also counts toward: Command-line interface

release

  • Adds Cloudflare credential verification without a full resource fetch. v1.5.0 · Oct 2026 · source · release history
  • Adds AWS keyless authentication via IRSA and EC2 instance profiles, removing the need to store long-lived credentials in provider-config.yaml. v1.5.0 · Oct 2026 · source · release history
  • GCP short-lived credentials support added for authenticating with GCP providers v1.3.0 · Jan 2026 · source · release history
  • Enables GCP provider to fallback to Application Default Credentials (ADC) when gcp_service_account_key is not set v1.0.9 · Aug 2024 · source · release history
  • Adds --aws-assume-role support to the AWS provider for pulling assets from cross/multiple accounts v1.0.9 · Aug 2024 · source · release history
Kubernetes configuration and authentication support shipped suggested Allows the cyber tool to connect to Kubernetes clusters by supporting encoded kubeconfig injection, environment variable storage for secrets, and short-lived GCP credentials. 2 releases · 2 other sources · first seen Apr 2023

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

release

  • Adds the kubeconfig_encoded config option to provide K8s cluster configuration as base64-encoded content v1.0.7 · Feb 2024 · source · release history
  • gke (GCP) provider support for listing assets in Google Kubernetes Engine v1.0.3 · Apr 2023 · source · release history

example

  • Store the Kubernetes config in a secret or environment variable and reference it during execution. export KUBECONFIG_ENCODED=$(base64 /path/to/kubeconfig) && cloudlist -c 'providers: [{ type: kubernetes, kubeconfig_encoded: "$KUBECONFIG_ENCODED" }]' v1.0.7 · Feb 2024 · source
  • Run cloudlist in environments where you cannot mount a kubeconfig file, by passing the encoded config directly. cloudlist -c 'providers: [{ type: kubernetes, kubeconfig_encoded: "<base64-string>" }]' v1.0.7 · Feb 2024 · source
Service-specific filtering shipped suggested Enables users to filter which specific cloud services are included in the asset listing via configuration files. 2 releases · first seen Aug 2024

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Adds service filter support via config file to control which cloud services are included in listing. v1.2.1 · Mar 2025 · source · release history
  • Adds the -s / -service CLI flag to filter or fetch assets by service name (comma-separated) v1.0.9 · Aug 2024 · source · release history
Self-update capability shipped Automates the process of updating the cyber tool to the latest version via CLI flags or internal commands. 1 release · 1 other source · first seen Apr 2023

Also counts toward: Command-line interface

release

  • --self-update CLI flag to enable automatic tool self-updates v1.0.3 · Apr 2023 · source · release history

example

  • Automate updating cloudlist to the latest version via CLI. cloudlist --self-update v1.0.3 · Apr 2023 · source
Custom provider sources shipped Allows fetching subdomains or other assets from custom sources such as URLs, extending beyond standard cloud providers. 1 release · first seen Feb 2025

Shared capability: Subdomain enumeration

release

  • Adds custom provider support to fetch subdomains from URLs v1.2.0 · Feb 2025 · source · release history
Dual-stack IP discovery shipped suggested Enables the discovery of both IPv4 and IPv6 addresses for compatible providers and services. 1 release · first seen Feb 2025

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

release

  • Enables dual-stack IP discovery (IPv4 and IPv6) for compatible providers and services v1.2.0 · Feb 2025 · source · release history
Cloudlist version management verified Allows users to update cloudlist to the latest version from the command line. 1 other source · first seen Aug 2024

Also counts toward: Command-line interface

command line

Environment variable resolution in configuration shipped Supports resolving secrets and configuration values from environment variables at runtime within provider configuration blocks. 1 release · first seen Nov 2022

release

  • Adds environment variable support to provider configuration blocks so secrets like $AWS_ACCESS_KEY can be resolved at runtime v1.0.2 · Nov 2022 · source · release history
Automated configuration initialization shipped Creates a default provider configuration file automatically on the first run to simplify initial setup. 1 release · first seen Jun 2022

release

  • Creates a default provider configuration file automatically on first run to simplify initial setup. v1.0.1 · Jun 2022 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for cloudlist, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail cloudlist puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Commercials

pricing & packaging history · ProjectDiscovery vendor page

23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

projectdiscovery.io, every change

ProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What cloudlist connects to, runs on and detects, read from its release notes and docs. So far: 9 updated integrations, 1 new integration.

Show

10 changes, tracked since Oct 14, 2026.

  • Oct 142026

    new OVH DNS provider

    Added OVH DNS provider by @ysokolovsky in https://github.com/projectdiscovery/cloudlist/pull/696

    v1.5.0 Source ↗

  • Oct 142026

    updated AWS new resource types: Elastic IPs, RDS endpoints, ElastiCache endpoints

    Added AWS Elastic IPs by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/777 - Added AWS RDS endpoints by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/778 - Added AWS ElastiCache endpoints by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/786

    v1.5.0 Source ↗

  • Oct 142026

    updated Azure new resource types: Service Fabric clusters, managed database endpoints

    Added Azure Service Fabric clusters by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/779 - Added Azure managed database endpoints by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/780

    v1.5.0 Source ↗

  • Oct 142026

    updated GCP new resource types: addresses and forwarding rules

    Added GCP addresses and forwarding rules by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/781

    v1.5.0 Source ↗

  • Oct 142026

    updated Hetzner new resource types: load balancers, floating and primary IPs

    Added Hetzner load balancers, floating and primary IPs by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/782

    v1.5.0 Source ↗

  • Oct 142026

    updated Scaleway new resource types: flexible IPs, load balancers, serverless, Kapsule

    Added Scaleway flexible IPs, load balancers, serverless and Kapsule by @dogancanbakir in https://github.com/projectdiscovery/cloudlist/pull/783

    v1.5.0 Source ↗

How we count

Read from 1 of 14 release notes and docs updates we hold for cloudlist. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through cloudlist's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Coverage in all entries

14 entries

  1. October 20261
  2. February 20261
  3. January 20261
  4. April 20251
  5. March 20251
  6. February 20251
  7. August 20241
  8. March 20241
  9. February 20241
  10. October 20231
  11. April 20231
  12. November 20221
  13. June 20221
  14. February 20221
    Coverage in all entries

    14 entries

    Project health

    Issue, contributor and maintainer activity in projectdiscovery/cloudlist, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 15 +6 vs prior 12 months
    2. Maintainers 2 +3 joined · −3 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 39% of issues opened, last 12 months
    5. Median time to close 1 day first maintainer reply 17 hours
    6. Open backlog 1 of 77 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 1
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,052
    Issue themes, last 12 months
    • bugs 8%
    • features 8%
    • other 84%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →