otinstaller · Domain and DNS

Install cloud_enum on Linux in one command

cloud_enum takes a keyword such as a company name and checks whether storage buckets, apps, and other public resources with that name exist on AWS, Azure, and Google Cloud. It reports what is open versus protected.

cloud_enum in three lines

pipx install otinstaller
ot install cloud-enum
ot run cloud-enum -- d:example.com

Runs initstring/cloud_enum (MIT, ★ 2.1k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What cloud_enum is for

Finding exposed buckets named after a brand.
Checking your own cloud footprint for leftovers.

Typed inputs for cloud_enum

otinstaller translates these prefixes into cloud_enum's own flags. Anything else after -- is passed through unchanged, so every original flag still works.

d:: domain · ot run cloud-enum -- d:example.com

It also takes ip input through its own flags; there is no typed prefix for those yet.

Run every installed tool that takes the same input at once: ot run --all d:example.com

Where the results go

Every run lands under ./results/cloud-enum/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff cloud-enum <target>, and pull indicators out with ot extract.

Before you run it

Pass the keyword with the original -k flag for anything beyond a plain domain name.

Update, remove, inspect

ot info cloud-enum      # inputs, flags, keys
ot example cloud-enum   # sample output
ot update cloud-enum    # move to the next tested version
ot remove cloud-enum    # delete its virtualenv

Full reference for this tool: docs for cloud-enum.

Pairs with

BBOT

BBOT is a recursive scanner that starts from a domain or IP, discovers subdomains, hosts, and services, and feeds each finding back in as a new target.

FinalRecon

FinalRecon runs a set of web recon checks against a URL in one go: headers, SSL certificate, WHOIS, crawler, DNS, subdomains, directory search, and a port scan.

secator

secator wraps dozens of recon and scanning tools behind one command with a shared output format, and runs them as tasks, workflows, or full scans.

FAQ

cloud_enum with otinstaller, answered

How do I install cloud_enum on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install cloud-enum. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.

Which inputs does cloud_enum take through otinstaller?

d: (domain). otinstaller maps each prefix to cloud_enum's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.

Where does otinstaller save cloud_enum results?

Under ./results/cloud-enum/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff cloud-enum <target> to compare the last two.

Does cloud_enum need an API key or a login?

No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.

Can I run cloud_enum together with other tools?

Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including cloud_enum. Save the combination as a playbook to repeat it.