# Install basti with Homebrew

Securely connect to RDS, Elasticache, and other AWS resources in VPCs. Version 1.8.0 via Homebrew; verified 2026-06-15.

## Install

```sh
sudo av install brew:basti
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install basti
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:basti
- **Package manager:** Homebrew
- **Version:** 1.8.0
- **Source summary:** Securely connect to RDS, Elasticache, and other AWS resources in VPCs
- **Homepage:** <https://www.basti.app>
- **Last updated:** 2026-06-15T10:20:10-04:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- basti (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.8.0
## Project history and usage

Basti is an AWS-focused CLI for securely reaching private VPC resources such as RDS, Aurora, ElastiCache, and custom TCP targets. The README says the name comes from bastion host and emphasizes no idle costs, no SSH keys, and IAM-driven access.

### Project history

The npm package metadata shows the public `basti` package was created on 2022-06-13. The GitHub README describes a tool that wraps AWS Session Manager port forwarding and automates the bastion EC2 lifecycle needed to reach private network resources.

The project later added a CDK companion package, `basti-cdk`, and continued through 1.x releases. npm metadata shows active releases from 1.5.0 in 2023 through 1.8.0 on 2026-05-17.

### Adoption history

Basti's adoption niche is teams that want database and cache access in private AWS VPCs without a permanently running bastion host, direct inbound SSH, or hand-maintained Session Manager setup. The README explicitly targets local machines and CI/CD pipelines.

The supplied package facts show Homebrew packaging, while the README documents npm installation and Homebrew installation. The README's badges also point to npm version and total-download signals.

### How it is used

The documented flow is `basti init` once per target to create or reuse the bastion resources, then `basti connect` to start a local port-forwarding session. A user can then connect to the resource on localhost, for example with `psql -h localhost -p 5432`.

Basti uses AWS SDK credential resolution and is expected to work when AWS CLI credentials work. It supports interactive and automatic modes, config files named `.basti.yaml`, `.basti.yml`, or `.basti.json`, AWS profile and region options, and custom TCP targets.

### Why package nerds care

Basti is package-nerd significant because it packages a common cloud operations pattern into a single CLI: ephemeral bastion setup, Session Manager port forwarding, local TCP access, and cleanup. The value is not a new protocol, but removing recurring glue scripts around AWS infrastructure.

Its Homebrew formula matters because cloud operators often install this kind of tool beside `aws`, `psql`, `redis-cli`, and IaC CLIs rather than inside an application dependency tree.

### Timeline

- 2022-06-13: npm registry metadata records creation of the `basti` package.
- 2023-08-29: npm metadata records version 1.5.0.
- 2023-09-12: npm metadata records version 1.6.0.
- 2024-09-27: npm metadata records version 1.7.0.
- 2026-05-17: npm metadata records version 1.8.0.
- 2026: Current README documents Homebrew and npm installation, Basti CDK, config files, and Session Manager-based access.

### Related projects

- Related official technologies include AWS Systems Manager Session Manager, AWS SDK credential resolution, AWS CLI credential files, AWS CDK through the `basti-cdk` package, and AWS services such as RDS, Aurora, ElastiCache, EC2, and VPC networking.

### Sources

- <https://github.com/basti-app/basti/blob/main/README.md>
- <https://github.com/basti-app/basti/blob/main/docs/reference/cli.md>
- <https://registry.npmjs.org/basti>
- source_facts.package-manager


## Security Notes

No matching local secret-handling manifest was found for basti. Nucleus package metadata is still published here so future coverage has a stable package URL.



## 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

- Unix: ./.basti.yaml, ./.basti.yml, ./.basti.json

## Credential files

- Unix: ~/.aws/credentials
- Windows: %USERPROFILE%\.aws\credentials

## Combined YAML source

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


## Sources

- 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
