# flintrock を Homebrew でインストール

flintrock のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:flintrock
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install flintrock
```

  証拠: local Homebrew formula metadata

## パッケージ情報

- **パッケージキー:** brew:flintrock
- **パッケージマネージャ:** Homebrew
- **バージョン:** 2.1.0
- **ソース概要:** Tool for launching Apache Spark clusters
- **ホームページ:** <https://github.com/nchammas/flintrock>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- flintrock (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 2.1.0
## プロジェクトの歴史と使われ方

Flintrock is a command-line tool for launching Apache Spark clusters, especially short-lived EC2 clusters for experimentation, performance testing, and automated pipelines.

### プロジェクトの歴史

The README explicitly positions Flintrock as a faster, better alternative to spark-ec2. Its motivation section says spark-ec2 made Spark accessible but had pain points around launch speed, missing config files, non-resizable clusters, and custom machine images.

Flintrock developed into a Python CLI with YAML configuration, subcommands for launch, destroy, login, describe, add-slaves, remove-slaves, run-command, and copy-file, and support for current Spark and Hadoop/HDFS defaults.

### 採用の歴史

The project README lists external talks, guides, and papers that used or discussed Flintrock, including a Spark Summit talk titled 'Flintrock: A faster, better spark-ec2'.

Official install guidance centers on pipx/PyPI and GitHub releases, while the README notes Homebrew as a community-supported distribution that may be out of date.

### 使われ方

A typical workflow is to run flintrock configure, save EC2 and Spark defaults into config.yaml, launch a cluster, work on Spark, and destroy the cluster afterward.

The README recommends IAM roles for S3 access rather than copying AWS credentials to clusters, and describes Flintrock as unsuitable for permanent infrastructure or non-Spark Hadoop services.

### パッケージ好きにとっての重要性

Flintrock is notable in package history as a CLI that wrapped a complicated cloud data workflow into a user-level package instead of a long-lived infrastructure framework.

Its packaging story also shows the boundary between official Python application distribution and community package-manager formulas: the project points users to pipx for current releases and marks Homebrew as community supported.

### タイムライン

- 2016: Release v0.7.0 was published.
- 2017: Release v0.9.0 was published.
- 2020: Release v1.0.0 was published.
- 2021: Release v2.0.0 was published.
- 2023: Release v2.1.0 was published and standalone builds stopped after this line according to the README.

### Related projects

- Flintrock is directly related to Apache Spark, Hadoop/HDFS, Amazon EC2, spark-ec2, and S3A access through Hadoop.
- The README contrasts Flintrock with permanent-infrastructure tools such as Terraform, Ansible, Ubuntu Juju, Databricks, Amazon EMR, and Apache Bigtop.

### ソース

- <https://api.github.com/repos/nchammas/flintrock/releases>
- <https://github.com/nchammas/flintrock>


## セキュリティノート

infrastructure mutation or orchestration signal.

- **Geiger リスク:** orange / 中
- 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.


## Configuration files

- Linux: $XDG_CONFIG_HOME/Flintrock/config.yaml, ~/.config/Flintrock/config.yaml
- macOS: ~/Library/Application Support/Flintrock/config.yaml

## Combined YAML source

View the package source record on GitHub. [combined/flintrock.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flintrock.yml)


## ソース

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