
I like how intuitive the deployment workflow is. Connecting a Git repository takes just a few clicks, and preview environments let me test changes before merging to production. Amplify’s built-in Git deployments, hosting with SSL, and automatic build setup make it quick to get applications running without configuring heavy infrastructure from scratch. I also like the out-of-the-box Cognito authentication and the easy connection to Lambda and API Gateway, which save development time and let me focus on core features instead of infrastructure glue. The Gen 2 setup was straightforward, and per-developer cloud sandboxes let me configure authentication and test the backend locally right away. Since our other infrastructure is already on AWS, using Amplify also simplifies IAM and billing and gives us direct integration with AWS services. For teams building on AWS, I find it a productivity booster without heavy DevOps overhead. Review collected by and hosted on G2.com.
I find the learning curve steep once I step outside standard workflows. Debugging CloudFormation failures and IAM permission issues can get complicated fast, and advanced backend configurations feel restrictive compared with using raw AWS CDK or Terraform. It can also be tricky to predict costs across Cognito, Lambda, CloudFront, and build minutes as traffic scales. The transition between Amplify Gen 1 and Gen 2 documentation can be confusing, and setting up IAM permissions and local CLI credentials for new team members adds some minor onboarding friction. Review collected by and hosted on G2.com.


