pkg.soopen package index

brew / Rang 2599

awslogs mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für awslogs in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install awslogs

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#awslogs

nixpkgs package indexes · pkgs/by-name/aw/awslogs/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Simple command-line tool to read AWS CloudWatch logs

Befehle und Aliase

  • awslogs

Verlauf

Projektgeschichte und Nutzung

awslogs is a command-line reader for Amazon CloudWatch Logs. It wraps common log-group, log-stream, tailing, filtering, and time-window workflows in a small CLI aimed at humans using pipes and terminal tools.

Projektgeschichte

The `jorgebastida/awslogs` repository was created in January 2015, shortly after CloudWatch Logs became a common AWS logging destination. The README describes it as a simple tool for querying groups, streams, and events from Amazon CloudWatch Logs, with features such as aggregation across streams, colored output, watching logs, and human-friendly relative time filters.

The project used Git tags rather than GitHub releases for much of its history. Tags show early 0.x releases by 2016 and a 0.15.0 tag in 2024, while the README continues to document both pip and Homebrew installation.

Adoptionsgeschichte

awslogs became popular because it made CloudWatch Logs feel closer to `tail`, `grep`, and other local log-reading workflows. Before and alongside newer AWS CLI log commands and consoles, it gave operators a direct way to stream and search CloudWatch logs from a terminal.

Its public repository attention and package-manager availability reflect a narrow but durable use case: AWS users wanted log access that fit shell habits.

Wie es verwendet wird

Common usage includes `awslogs groups`, `awslogs streams GROUP`, and `awslogs get GROUP STREAM_EXPRESSION`, often with `--start`, `--end`, `--watch`, `--filter-pattern`, or `--query`. The README highlights piping output into tools such as `grep` for pseudo-realtime monitoring.

awslogs can take explicit AWS access keys, but its README recommends using AWS CLI-managed credentials when available; with multiple profiles, users pass `--profile` or set `AWS_PROFILE`.

Warum Paket-Nerds sich dafür interessieren

awslogs matters to package-manager users as a classic single-purpose cloud CLI: small command surface, obvious executable name, and immediate value in incident-response shells. It represents the era when many AWS service gaps were filled by independent Python CLIs distributed through pip and Homebrew.

For package nerds, it is also a useful contrast with AWS CLI: not every AWS task wants a giant generated vendor CLI when a focused stream-oriented tool is nicer.

Zeitleiste

  • 2015: Public GitHub repository `jorgebastida/awslogs` created.
  • 2016: 0.5 tag published.
  • 2024: 0.15.0 tag published.
  • 2024: Repository still receives updates.

Related projects

  • AWS CLI can also retrieve CloudWatch Logs through generated service commands.
  • Amazon CloudWatch Logs is the AWS service queried by awslogs.
  • Boto/Boto3 and AWS shared credentials provide the underlying AWS Python ecosystem and credential conventions.

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

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
awslogsExecutableindexiertes ExecutableAus 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.15.0
Manager aktualisiert2026-05-12
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:awslogs
Version0.15.0
PaketmanagerHomebrew
Homepagehttps://github.com/jorgebastida/awslogs
Repositoryhttps://github.com/jorgebastida/awslogs
Zuletzt aktualisiert2026-05-12T10:32:03Z
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

awslogs

nix profile install nixpkgs#awslogs
  • normalized package name match
  • Abgeglichen nach: Awslogs
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/aw/awslogs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation