Automic VaultAutomic Vault

brew

Install aws-amplify with Homebrew, scoop

Build full-stack web and mobile apps in hours. Easy to start, easy to scale. Version 14.5.1 via Homebrew; verified 2026-06-26.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install aws-amplify

local Homebrew formula metadata

Windows

Scoopverified · 92%
scoop install main/aws-amplify

Scoop official bucket manifest trees · bucket/aws-amplify.json · source: api.github.com

overview

Package summary

Build full-stack web and mobile apps in hours. Easy to start, easy to scale

Commands and aliases

  • amplify

history

Project history and usage

AWS Amplify CLI is the command-line toolchain for creating, integrating, and managing AWS-backed web and mobile app services. The Homebrew package installs the amplify command, historically centered on Amplify Gen 1 workflows such as amplify init, add, push, pull, and env management.

Project history

AWS announced the AWS Amplify library and AWS Mobile CLI in 2017, and that announcement now carries an editorial note directing users to the AWS Amplify CLI. In August 2018, AWS announced the Amplify CLI toolchain as the newer workflow for configuring local project state and deploying cloud resources.

The Amplify CLI's Gen 1 architecture used AWS CloudFormation and nested stacks so developers could add or modify backend configurations locally before pushing them to an AWS account. Its file layout grew around an amplify/ project directory containing backend state, team environment metadata, feature flags, and generated client configuration.

Amplify later introduced Gen 2, a code-first TypeScript backend experience built on AWS CDK constructs. AWS made Amplify Gen 2 generally available on May 6, 2024, which shifted new projects toward ampx and file-based TypeScript backend definitions while leaving Gen 1 CLI documentation in maintenance mode.

Adoption history

Amplify CLI was adopted heavily by frontend and mobile developers who wanted AWS-backed auth, APIs, storage, functions, and hosting without hand-writing all of the CloudFormation. Its category model let users add Cognito, AppSync, S3, Lambda, and hosting resources from prompts and then commit the resulting project files.

The tool also became a source of package-manager friction because it is an npm-distributed CLI with a large plugin ecosystem, but many users want it installed like any other system command. Homebrew and Scoop formulas serve that audience by making amplify available outside a per-project node_modules tree.

How it is used

In Gen 1 workflows, users run amplify configure to connect local tooling to an AWS account, amplify init to create an Amplify project, amplify add <category> to model backend resources, and amplify push to deploy generated CloudFormation. The CLI writes project state under amplify/ and consumes AWS shared config and credentials files for account access.

Amplify's documented project files include amplify/.config/, backend-config.json under both amplify/backend and amplify/#current-cloud-backend, team-provider-info.json, cli.json, category cli-inputs.json files, generated client configuration, and deployment secrets stored outside the repository. Gen 2 workflows instead use npx ampx commands and generate amplify_outputs.json for client configuration.

Why package nerds care

For package nerds, aws-amplify is a case study in packaging a fast-moving JavaScript cloud CLI as a system formula. It has to bridge npm expectations, Node version support, AWS credentials, generated project files, and the fact that the product line split between Gen 1 CLI and Gen 2 ampx workflows.

It is also historically useful because old Amplify projects often encode their backend state in generated JSON files. Having a reproducible CLI installation can be the difference between being able to pull, inspect, migrate, or retire an older Amplify backend.

Timeline

  • 2017: AWS announced AWS Amplify and the AWS Mobile CLI, with later guidance to use Amplify CLI going forward.
  • 2018: AWS announced the AWS Amplify CLI toolchain.
  • 2021: AWS Amplify CLI added support for function environment variables and secrets.
  • 2024: AWS Amplify Gen 2 became generally available as a fullstack TypeScript experience.
  • 2027: AWS Amplify Gen 1 documentation says Gen 1 reaches end of life on May 1, 2027.

Related projects

  • AWS Amplify Gen 2 backend tooling uses the @aws-amplify/backend-cli package and ampx commands.
  • AWS CDK underpins Amplify Gen 2's backend-building model and can be used for custom resources.
  • AWS CloudFormation is the deployment substrate used by the Gen 1 CLI and nested-stack architecture.

Sources

security posture

No protected-tool coverage found yet

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

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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.

Configuration files

Config paths the tool may read or write during local use.

Unix
amplify/.config/amplify/backend/backend-config.jsonamplify/#current-cloud-backend/backend-config.jsonamplify/team-provider-info.jsonamplify/cli.jsonamplify/**/cli-inputs.json~/.aws/amplify/deployment-secrets.json

Credential files

Credential-bearing paths to review before unattended agent runs.

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

executables

Installed executables

CommandKindExposureNote
amplifycliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version14.5.1
manager updated2026-06-26
local dataok
upstreamnot checked
latest detectednot detected

https://aws.amazon.com/amplify/

install metadata

Package metadata

Package keybrew:aws-amplify
Version14.5.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/aws-amplify
Homepagehttps://aws.amazon.com/amplify/
Repositoryhttps://github.com/aws-amplify/amplify-cli
Upstream docshttps://docs.amplify.aws/gen1/javascript/tools/cli
LicenseApache-2.0
Source archivehttps://registry.npmjs.org/@aws-amplify/cli-internal/-/cli-internal-14.5.1.tgz
Last updated2026-06-26T15:54:25Z
Pulseupdated
Dependenciesnode
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameaws-amplify
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Scoop95%

main/aws-amplify

scoop install main/aws-amplify
  • normalized package name match
  • Matched by: Aws Amplify
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/aws-amplify.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment