macOS
Homebrewverifiziert · 100%
brew install cloud-nukeprovider-native install command
brew / Rang 2198
cloud-nuke mit Homebrew installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cloud-nuke in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
CLI tool to nuke (delete) cloud resources
Projektlinks
Befehle und Aliase
- cloud-nuke
Verlauf
Projektgeschichte und Nutzung
cloud-nuke is Gruntwork's destructive cleanup CLI for deleting cloud resources, mainly used around test accounts, ephemeral infrastructure, and default AWS resource cleanup. Its history is source-backed enough to treat it as a real package-manager tool rather than just a GitHub utility.
Projektgeschichte
The gruntwork-io/cloud-nuke repository was created in 2017 and is maintained by Gruntwork. The README frames the tool as a way to remove leftover resources, clean test accounts, and delete defaults such as default VPCs and permissive security group rules.
The tool evolved from AWS-focused cleanup into a CLI with inspect, dry-run, filtering, config-file, and GCP commands. The README also documents telemetry added as of v0.29.0, showing a maintained packaged CLI rather than a one-off script.
Adoptionsgeschichte
Official installation docs point users to GitHub release binaries and explicitly list Homebrew for macOS and Linux plus winget for Windows. The input package-manager facts also record Nix, Scoop, and winget identifiers, so adoption is package-manager centric even though upstream cautions that package-manager builds may lag releases.
The CLI is significant in infrastructure shops because it turns account cleanup into a repeatable command with filters, dry-run, region selection, resource-type selection, and config-driven targeting.
Wie es verwendet wird
Common use is `cloud-nuke aws` for deletion, `cloud-nuke inspect-aws` for inspection, `cloud-nuke defaults-aws` for default VPC and security group cleanup, and `cloud-nuke gcp` for GCP deletion. The official docs emphasize dry-run and filtering because the default delete path is intentionally dangerous.
Credentials come from standard AWS CLI credential mechanisms for AWS usage, and the tool accepts command flags plus an optional user-supplied config file path for granular filtering.
Warum Paket-Nerds sich dafür interessieren
cloud-nuke is a good example of a high-blast-radius CLI where package freshness, binary provenance, and default behavior matter. Upstream warns users to compare package-manager versions with GitHub releases.
For Homebrew and cross-platform package indexes, it is notable because it packages operational cloud deletion behavior as a one-command executable rather than a library.
Zeitleiste
- 2017: gruntwork-io/cloud-nuke GitHub repository metadata was created.
- v0.29.0: Upstream README records the addition of telemetry.
- Current docs: Official install instructions list release binaries, Homebrew, and winget.
Related projects
- Gruntwork's broader infrastructure tooling ecosystem is the upstream context for cloud-nuke.
- AWS CLI credential files and GCP project credentials are operational dependencies for the supported cloud providers.
- Cloud clean-up and account janitor tools occupy the same niche, but cloud-nuke is the package in this batch with explicit package-manager distribution.
Quellen
Sicherheitslage
Risikostufe: orange
infrastructure mutation or orchestration signal.
Risikoklassifikator
orange Risiko · mittel Konfidenz · infrastructure
Warum
- infrastructure mutation or orchestration signal
Signale
- text:cloud
Installationsverhalten
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.aws/credentials~/.aws/config- Windows
%UserProfile%\.aws\credentials%UserProfile%\.aws\config
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
cloud-nuke | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-08-03
Manager-Version0.52.0
Manager aktualisiert2026-07-27
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:cloud-nuke |
|---|---|
| Version | 0.52.0 |
| Paketmanager | Homebrew |
| Homepage | https://gruntwork.io/ |
| Repository | https://github.com/gruntwork-io/cloud-nuke |
| Zuletzt aktualisiert | 2026-07-27T22:04:01+02:00 |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Geiger risk classifier
- Nucleus package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation