# Install awslogs with Homebrew, Nix Simple command-line tool to read AWS CloudWatch logs. Version 0.15.0 via Homebrew; verified 2026-05-12. Also installable with nix: nix profile install nixpkgs#awslogs. ## Install ```sh sudo av install brew:awslogs ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install awslogs ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#awslogs ``` Evidence: nixpkgs package indexes: pkgs/by-name/aw/awslogs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:awslogs - **Package manager:** Homebrew - **Version:** 0.15.0 - **Source summary:** Simple command-line tool to read AWS CloudWatch logs - **Homepage:** - **Repository:** - **Last updated:** 2026-05-12T10:32:03Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - awslogs (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.15.0 ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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`. ### Why package nerds care 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. ### Timeline - 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. ### Sources - - - - - - ## Security Notes infrastructure mutation or orchestration signal. - **Geiger risk:** orange / medium - infrastructure mutation or orchestration signal ## 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 - Unix: ~/.aws/credentials ## Other Package-Manager Records - Nix - awslogs: normalized package name match | nixpkgs package indexes: pkgs/by-name/aw/awslogs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/awslogs.yml](https://github.com/mxcl/pkgdb/blob/main/combined/awslogs.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph