AWS Amplify Reviews

Static & frontend hosting

27 reviews
AWS Amplify
60signal
i

A score out of 100. Negative and mixed reviews take points off, and so does having only a few reviews, so a handful of glowing reviews can’t beat a product many people like.

27reviews

What customers love, and what they don’tWhat customers noticed

Also mentioned: best for developers14

Customer reviews (27)

Add your review

Showing 14 reviews mentioning best for developers Show all

Moving many sites to it cut hosting costs by 60 to 70 percent compared to Vercel, but brought poor UX, slow builds and time-consuming configuration.

Two years of building a tutoring platform ended in migrating to Supabase because DynamoDB lacked SQL joins and Cognito authentication was a pain.

Very opinionated, with CI/CD that does not allow Docker-in-Docker builds, so only the hosting part is used alongside CDK, which keeps switching easy.

Powerful for IoT apps and deep AWS integrations with Lambda, DynamoDB, and Cognito, though DataStore and initial setup are much trickier than Firebase.

Combining it for auth and GraphQL queries alongside CDK v2 works well in theory, though documentation gaps force heavy reliance on tutorials.

Multiple MVP and proof-of-concept apps built with Cognito auth ran without a single issue, and customizing styling or building your own React auth forms is straightforward.

Once past the initial learning curve, YAML-driven DynamoDB creation, GraphQL API code generation, and unified AWS billing make development much easier.

GraphQL schema management is unfriendly and connecting to Aurora SQL requires custom VTL resolvers with major feature gaps.

Used for the React frontend deploy with a Lambda backend and working well, with different accounts per environment and infrastructure kept in Terraform, and no issues.

Custom build images and configuration turned into a frustrating rabbit hole that wasn't worth the effort compared to switching to Vercel.

Skipping the CLI and prepackaged forms in favor of the front-end JS libraries and Serverless Stack CDK made auth signups, logins, and password resets work with zero issues.

Front-end libraries connect cleanly to self-configured user pools and APIs for mobile apps, beating the standalone Cognito JS library by a mile.

Acts as a thin UI wrapper around conventional AWS that is hard to use without a pretty deep understanding of the underlying services it sets up.

Common questions about AWS Amplify

Is AWS Amplify worth it?

Of the 8 reviews with a clear verdict, 25% are positive, 25% mixed and 50% negative. The praise mentioned most is easy to use. The most common complaint is resource limits.

What do people like about AWS Amplify?

The praise reviewers mention most: easy to use (5 reviews), reliable (4 reviews) and great value (2 reviews). For example: Hosts three of their websites and finds it convenient to keep builds, Route53 domain purchase and DNS in one place.

What are the most common complaints about AWS Amplify?

The complaints reviewers mention most: resource limits (4 reviews), outages (3 reviews) and slow (2 reviews). For example: Next.js on-demand revalidation did not work at all during testing, adding frustrating DevOps overhead.

What does the signal score of 60 mean?

It's how well reviewed AWS Amplify is, out of 100. Negative and mixed reviews take points off, and so does having only a few reviews: a service needs plenty of them, compared with the most-reviewed services here, to reach the high 80s and 90s. It's worked out from reviews only, needs at least 5 of them, and updates as new ones come in.

What are the specs of AWS Amplify?

Category: Static & frontend hosting.

Where do these AWS Amplify reviews come from?

27 are quotes from Reddit, each linked to the original. Customer reviews are checked for spam before they appear. Every review, written here or quoted, is read as positive, mixed or negative.

Discover more static

See all static