Reporting Bugs/Feature Requests

[!Important]

Amplify Gen 2 is now generally available

If you are starting a new project, we recommend starting with Amplify Gen 2.

If you are an existing Gen 1 customer, we encourage you to start migrating to Gen 2 using the migration guide and tooling.

⚠️ Amplify Gen 1 is in Maintenance Mode

Amplify Gen1 is in maintenance mode. Starting May 1, 2026, Gen 1 backends will receive only critical bug fixes and security patches and will reach end of life on May 1, 2027. Migrate your backend to Amplify Gen 2 using the migration guide and tooling to continue receiving new features and support.

AWS Amplify CLI (Gen 1)

The AWS Amplify CLI is a toolchain which includes a robust feature set for simplifying mobile and web application development. The CLI uses AWS CloudFormation and nested stacks to allow you to add or modify configurations locally before you push them for execution in your account.

• Install the CLI
• Commands Summary
• Tutorials
• Contributing
• Start building your app
• Changelog

Install the CLI

• Requires Node.js® version 22 or later

Install and configure the Amplify CLI as follows:

$ npm install -g @aws-amplify/cli
$ amplify configure

Commands Summary

The Amplify CLI supports the commands shown in the following table.

Category specific commands:

• auth (Amazon Cognito)
• storage (Amazon S3 & Amazon DynamoDB)
• function (AWS Lambda)
• api (AWS AppSync & Amazon API Gateway)
• analytics (Amazon Pinpoint)
• hosting (Amazon S3 and Amazon CloudFront distribution)
• notifications (Amazon Pinpoint)
• interactions (Amazon Lex)
• predictions (Amazon Rekognition, Amazon Textract, Amazon Translate, Amazon Polly, Amazon Transcribe, Amazon Comprehend, and Amazon SageMaker)

Tutorials

• Getting Started guide
• GraphQL transform tutorial
• Native development with Amplify CLI and AWS AppSync

Developing

To set up your local development environment, go to Local Environment Setup.

To test your category, do the following:

cd <your-test-front-end-project>
amplify-dev init
amplify-dev <your-category> <subcommand>

Before pushing code or sending a pull request, do the following:

• At the command line, run yarn lint at the top-level directory. This invokes eslint to check for lint errors in all of our packages.
• You can use yarn lint to find some of the lint errors. To attempt fix them, go to the package that has errors and run yarn lint-fix
• If there are any remaining lint errors, resolve them manually. Linting your code is a best practice that ensures good code quality so it's important that you don't skip this step.

Contributing

We are thankful for any contributions from the community. Look at our Contribution Guidelines.