# 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 ```sh sudo av install brew:aws-amplify ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install aws-amplify ``` Evidence: local Homebrew formula metadata ### Windows - Scoop (92%): ```sh scoop install main/aws-amplify ``` Evidence: Scoop official bucket manifest trees: bucket/aws-amplify.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:aws-amplify - **Package manager:** Homebrew - **Package manager page:** - **Version:** 14.5.1 - **Source summary:** Build full-stack web and mobile apps in hours. Easy to start, easy to scale - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-06-26T15:54:25Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - amplify (cli) - amplify (alias) ## Dependencies - node ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 14.5.1 - Package-manager updated: 2026-06-26 - Local data: ok - Upstream repository: https://aws.amazon.com/amplify/ - info: Release/tag comparison is only available for GitHub repositories. ## 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 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 Notes 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. ## 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: amplify/.config/, amplify/backend/backend-config.json, amplify/#current-cloud-backend/backend-config.json, amplify/team-provider-info.json, amplify/cli.json, amplify/**/cli-inputs.json, ~/.aws/amplify/deployment-secrets.json ## Credential files - Unix: ~/.aws/credentials - Windows: %USERPROFILE%\.aws\credentials ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** aws-amplify - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Scoop - main/aws-amplify: normalized package name match | Scoop official bucket manifest trees: bucket/aws-amplify.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [node](https://www.automicvault.com/pkg/brew/node/) - Runtime dependency declared by Homebrew. - [amazon-ecs-cli](https://www.automicvault.com/pkg/brew/amazon-ecs-cli/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-cdk](https://www.automicvault.com/pkg/brew/aws-cdk/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-console](https://www.automicvault.com/pkg/brew/aws-console/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-elasticbeanstalk](https://www.automicvault.com/pkg/brew/aws-elasticbeanstalk/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-es-proxy](https://www.automicvault.com/pkg/brew/aws-es-proxy/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-google-auth](https://www.automicvault.com/pkg/brew/aws-google-auth/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-iam-authenticator](https://www.automicvault.com/pkg/brew/aws-iam-authenticator/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-keychain](https://www.automicvault.com/pkg/brew/aws-keychain/) - Shares av.db curated category or tags: aws, cli, cloud-infrastructure. - [aws-sam-cli](https://www.automicvault.com/pkg/brew/aws-sam-cli/) - Package names and metadata indicate a similar tool family. Shared terms: aws, build, cli, cloud, cloud-infrastructure. ## Combined YAML source View the package source record on GitHub. [combined/aws-amplify.yml](https://github.com/automic-vault/db/blob/main/combined/aws-amplify.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph