AWS Amplify Reviews

My main use case for AWS Amplify is to maintain and modify an amplified app that I created using React, which I built a few years ago. I had the opportunity to work through authentication, AppSync, DynamoDB, and deployment again. AWS Amplify makes it very easy for me to connect the front end and back end to AWS services like Cognito and DynamoDB.

A specific example of something I did with AWS Amplify in my app is when I built a platform that is live for a client, where I have a feature that can be accessed by anybody using authentication. Users have to log in through the web platform, for which I used AppSync and integrated GraphQL. AWS Amplify provides powerful features for building authentication flows, including signing in and resetting passwords, and it is very powerful once configured correctly.

In my day-to-day use of AWS Amplify, I manage user groups in GraphQL while ensuring that the production version of the app is running without failed builds. If there are any issues, I fix them. I can monitor this in AWS Amplify, which is a strong tool for building full-stack applications and supports not only web platforms but also other frameworks such as Android.

The best features AWS Amplify offers include AppSync, which is very good for authentication and the deployment version. It also allows me to easily use DynamoDB tables from AWS.

The authentication and deployment features of AWS Amplify help me by ensuring that the authentication flow runs smoothly, as they are integrated and interconnected with GraphQL. I can delete or add users, create groups, reset passwords, and customize the login experience using the sign-in and sign-out features that come with GraphQL. AWS Amplify also has IO components, allowing me to configure files for AWS export to check if there are any builds or configurations missing. The ease of using AppSync and GraphQL is what I appreciate most about AWS Amplify.

AWS Amplify is a strong tool for quickly building full-stack applications, which do require a solid understanding of how the underlying AWS services interact.

AWS Amplify has positively impacted my work by making things easier, faster, and more efficient, particularly with its continuous integration feature and user management while monitoring app builds. The usage of AWS Amplify is part of my freelance work for different clients rather than directly within a single organization.

There are certain things about AWS Amplify that keep changing. One aspect is that the DynamoDB table and user group API key expires in 365 days, which requires me to renew this API key to persist data. It would be ideal if there were no expiration limits. There are always workarounds in ensuring that I do not solely rely on the API key for database access by assigning specific groups for it.

I have been using AWS Amplify for over three years.

AWS Amplify is stable.

If I had to rate the scalability of AWS Amplify, I would give it a perfect rating of 100 out of 100.

I have used multiple different solutions for my projects before, but with this one, I sought a more organized and structured solution, which led me to AWS Amplify.

I see a return on investment from using AWS Amplify.

My experience with pricing, setup costs, and licensing is mostly with the free tier. I am paying only for the domain name and access to the DynamoDB table, which I find to be a pretty decent price.

Before choosing AWS Amplify, I evaluated options including hosting my React app on Heroku, using an S3 bucket on AWS, Elastic Beanstalk, or exploring Azure and other resources.

My advice for others looking into using AWS Amplify is to examine both the pros and cons and to check the documentation. I would rate this review a 9 out of 10.

I used AWS Amplify for a wedding video project to integrate a mobile app built with Flutter with AWS for uploading large video files, ranging from 2-3 GB up to 10-20 GB. I chose AWS Amplify because it was the best service to work with other AWS services I already used. It was very easy to implement with AWS S3 buckets, which I used to store and display the videos. AWS Amplify provided helpful features for uploading and downloading videos and setting up serverless commands to manage the process. I used the Amplify CLI to set up the storage components. While I used it with Flutter, AWS Amplify works well with other languages like React.

I like AWS Amplify's documentation. It's comprehensive and includes many examples, so you don't need to ask for help much - you can refer to the docs. It's easy to use. I also appreciate the cost structure. You only pay for what you use. For example, if you use 100 GB, you're charged for that, but if you don't use it, you pay the maintenance cost.

The only tricky part I experienced was during the initial installation. I followed the documentation, but it wasn't working for some reason. I had to modify some local files in the CLI-generated folder to get it to work. I had to dig deep to find the issue, and it wasn't mentioned in the docs. So, some issues could be better highlighted in the AWS CLI documentation, which would help developers integrate other services more easily. AWS needs to improve its support. 

I haven't encountered any stability issues. 

My company has 30 users. 

I used AWS Amplify because I was already using other AWS services, and it was suggested as the best option to integrate with those services. It was also a time-constrained project, so using the tool made sense rather than implementing other services or switching to third-party options.

For someone interested in using the tool for the first time, I'd say it's easier if you have good coding knowledge. For beginners, it can be challenging, and you'll need to figure things out as you go.

I'd rate the solution a five out of ten. As a new learner of AWS Amplify, I found it took time to learn and implement. For beginners, many services can be confusing to choose from. Choosing the wrong service can cost more time and money, which are crucial factors.

I use AWS Amplify along with AWS EC2, AWS Lambda, Amazon Pinpoint, and others. AWS Amplify, in particular, has been quite straightforward to use.

We've used AWS Amplify for several applications. Initially, it was for a specific project that required integration with third-party services and managing backend services. AWS Amplify was instrumental in managing AWS services like Amazon DynamoDB and others for us.

We use Amplify with our frontend (product) and backend (basically AWS). Amplify manages various AWS services for us, like DynamoDB, CloudFormation, and others. We customize it for our use case, of course. But let's say I want to add functionalities like antivirus or another database, or manage Lambda functions from the CLI or code. In those cases, we use the AWS console for those specific things. But Amplify is our main point of contact for backend changes through code, and it applies those changes seamlessly.

We have different environments like Dev, NetEnv, and UAT, so we need to change our configuration file depending on where we're deploying. The CLI handles this easily. 

Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as needed. They don't necessarily need to involve the cloud team for basic management.

For anything deeply related to settings, we involve them. But at the developer level, for common functionalities like setting up the initial tech stack (database, Lambda functions, notifications), Amplify with the CLI pretty much handles everything.

The Amplify CLI acts as a single source of truth. You install the SDK from there, and using the Amplify API, you can talk to and manage AWS services directly from your code. You don't need to go to the GUI and click through menus - everything is manageable through the Amplify API at the code level.

AWS Amplify integrates seamlessly with other services through AWS CloudFormation. Amplify first connects to the cloud for me. Whenever we write down the SDK, it's managed by CloudFormation. CloudFormation still happens on our cloud for your application because everything is updated with the help of cloud automation. 

Anything we need to change, we just add it to Amplify, and Amplify triggers the CloudFormation templates. Then it logs permission, updates the whole thing, or whatever you need it to ask.  

AWS can implement multiple web applications, and cross-platform applications, like iOS (AWS currently supports Android). They have Node.js, but they can also maybe integrate with cross-platform functionalities.  

I have been using it for two years. 

I would rate the stability an eight out of ten. If we face any issues, they can be addressed directly with AWS support. 

There are no big issues with Amplify itself. You just need to properly follow the documentation and set up everything for it to run smoothly. It can be a bit tricky initially.

Amplify manages app users and containers automatically. It scales similarly to other services, meaning you can scale properly depending on certain parameters like user upload and request access. 

However, Amplify doesn't directly manage application load balancing. You might need an Application Load Balancer in between to manage user load.

The customer service and support are fantastic. AWS depends on your plan and urgency. If you're in production and need support at that critical level, they'll support you quickly, digging deep into the main problem and how they can resolve it. 

They also try to resolve it from their end as well as with their main back-end team. They also implement a safe environment to test things if there's an AWS use case where nothing seems to work. Then, they'll guide you based on your criticality or priority.

Positive

In software development, we might use Flutter or any local front-end application. Then, we connect to services at AWS via the AWS SDK or various AWS APIs to manage the app. 

But Amplify simplifies everything by maintaining and managing AWS services with the application. It eliminates the need to install and manage third-party tools.

The initial setup can be a bit tricky at times, but it's pretty good overall. But sometimes, because we initially set up with your local Android Studio, your local service, it can take some time. 

If you've read the programming documentation and have enough resources, then it's easy for you. Or if you have an AWS subscription plan to get help from AWS, then, the setup is easy. 

Otherwise, you might need more clarity on simplification of how you set up with Amplify and how you can do so. Then, if you need other guidance at each step, how can you set it up, that is also a way to go. 

The pricing depends on what your use case is and whether you're an existing AWS customer. It's a pay-as-you-go model, so not expensive.

And for the free tier, you get 1,000 builds per minute, up to 5 gigabytes of storage on CDN, and no cost up to 15  gigabytes per month of data transfer. 

You can also get discounts for pushing 5 lakhs logs per month and one hundred million request durations per month. These offers are for the first month or year, and then their regular pricing kicks in. 

There are no charges below one dollar, but above one dollar, the cost depends on your specific requests and application usage.

Overall, I would rate the solution an eight out of ten. I would definitely recommend using this solution. 

I am a front-end heavy full-stack developer with five years of experience in web development. For the last two years, I have been working as a full-stack developer on a couple of projects. We used AWS Amplify as a backend service with the React tech stack. Amplify integrates features like GraphQL, DynamoDB, Cognito, AppSync, and Lambda functions. We required a solution that could accelerate the development process for a project with stringent deadlines, so we selected AWS Amplify for its comprehensive backend services.

Using AWS Amplify sped up our development process significantly. It provides an all-in-one solution for back-end infrastructure, which is crucial for delivering a project quickly to a client.

The most valuable feature is user management, which includes authentication and authorization. In addition to that, AWS Amplify offers a complete package with services like Cognito for multitenant applications and DynamoDB as a database solution, which makes everything work seamlessly together.

The documentation needs improvement, as it is not user-friendly and can be challenging for novices. Furthermore, the AWS user interface could be improved. Although AWS is making improvements, there are other solutions, such as Clerk, that provide a more streamlined and less expensive service than Cognito.

I have been using AWS Amplify for around two years.

If AWS Amplify is set up properly, it is quite stable. However, there is potential for user errors due to a lack of comprehensive documentation, which could destabilize the application.

AWS Amplify is scalable without any significant issues.

The support is good yet expensive. To get a proper and fast response, you need to have a premium license. Otherwise, you have to rely on the documentation to figure things out on your own.

Neutral

The initial setup for AWS Amplify is easy.

AWS Amplify and its associated services can become quite expensive. Besides the primary cost of Amplify, other costs include building and running Lambda functions, which can add up.

There are other solutions I'm finding better than AWS services. For example, Clerk provides authentication and authorizations and is very neat, clean, and less pricey.

It depends on who is asking. AWS Amplify might be suitable for some people and not for others.

I'd rate the solution five out of ten.

We use the solution in the backend to host applications. I used it for a short mini project where I was learning a bit of React Native. It was in React Native, where I was building an Uber Eats clone application with all three sides—the client side and the delivery side. We built out the three applications in React Native and used AWS Amplify for the backend. AWS Amplify is a very good tool to use. It provides a client command line interface that can be downloaded with NPM or Node modules. One thing I completely like is that they provide authentication services in a very good way. It supports two-factor authentication, Google sign-in, or any other sign-up/sign-in method. Nowadays, they also offer an Amplify UI, which you get out of the box when you install it on the project. Overall, it was a very great experience.

I didn't host my application but have used their backend as a service. It was a complete package with authentication, AWS AppSync, DynamoDB, and GraphQL. AWS Amplify is great if you don't know backend development and don't want to struggle with other backend services like MongoDB. You don't have to worry about what backend language or database to use. If you're confused, enroll with AWS Amplify. I also recommend Google Firebase for similar purposes.

These services provide the backend as a complete service. I really like that the solution integrates cloud services, so the data is real-time and starts quickly once the application loads. It has horizontal and vertical scaling that happens automatically.

For example, if you suddenly have 5,000 customers, it manages the sudden rise in usage. If there are only a few users, the solution decreases resources. It follows a pay-as-you-go model, so you are charged based on usage, like when you hit a certain number of clicks.

AWS has a very wide range of services, and AWS Amplify integrates these services. For example, it includes DynamoDB, also available as a standalone service.

I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs.

I have been using the solution for a year. 

I haven't had any issues with stability. However, when using the solution for the backend, you need to have your API key ready, as it doesn't automatically handle this by default.

AWS offers multiple services, but it can be costly. They charge you immediately if you exceed the free tier limits, such as over 10,000 clicks. I think there should be some notification before the charges apply, but instead, they bill you directly in your payment section.

I didn't contact their support team. There was a problem from the backend, but I resolved it using GitHub. Overall, the experience is good, and the support team resolves issues.

The solution's deployment is very easy. That's something I like about AWS Amplify. It's just like Firebase. You have to install the AWS Amplify command line interface through a library, and you can start using it.

I rate the overall solution a nine out of ten. I recommend using AWS Amplify. It's growing and has strong competitors like Firebase or Supabase, but AWS Amplify remains strong, especially with its strong backend services and servers. It provides fast, real-time performance. AWS Amplify is a good choice for beginners building an application or website. However, I recommend monitoring your usage to avoid unexpected charges and be aware that they may require a credit card for the initial setup.

Our primary use case is to leverage AWS Amplify for building and deploying web and mobile applications.

It has helped my organization by simplifying the development process and accelerating the time to market.

One of the things I like best about AWS Amplify is its ease of use and strong integration with other AWS services, which enhances efficiency.

AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options.

I have used the solution for a considerable period, which has allowed me to explore its features effectively.

AWS Amplify is easy to use, and I have never faced any issues with the stability while using Amplify.

The scalability of the solution is impressive, as it can seamlessly handle increasing workloads.

Customer service and support have been satisfactory, although there is room for improvement.

Positive

I switched from a previous solution to AWS Amplify due to its superior integration capabilities and user-friendly interface.

The initial setup was straightforward and did not pose any major challenges.

The implementation team was efficient and provided all the necessary support during the transition.

Our ROI has been positive, as AWS Amplify has significantly reduced development time and costs.

I find the pricing of AWS Amplify reasonable, considering the value it provides, although opinions may vary based on usage.

I evaluated other solutions before choosing AWS Amplify, but none matched its integration capabilities with AWS services.

I would recommend AWS Amplify to other people, particularly for its simplicity and robust feature set.

I'd rate the solution eight out of ten.

We and AWS are partners, and my colleague asked me if I wanted to do some small project just to evaluate the product, and then I stepped into it. We used it for a small project or PoC for quickly building a new application.

Together with Ionic and Amplify, a nice use case is when you want to generate the backend very fast, and you want to have a desktop application and mobile application. You can use Amplify to quickly create the frontend, and for the backend, you can drop your backend APIs, and then you can publish the desktop application on the cloud. To create the mobile application, you can use Ionic.

The link with Figma is very nice. You can create your design in Figma, and then you can import it into AWS Amplify and use it. You can link it to your data source and data bindings.

Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects.

A colleague of mine went to a conference in Las Vegas last year in November, and he mentioned AWS Amplify to me in January. In January, I did some research on a small project. 

It is getting more and more stable. When I was using it at the beginning of the year, it was a little bit unstable. I got some errors while importing the files from Figma, but it is getting better. When I was using it, it was still in beta. It has got a few more features now, and it is becoming more stable.

AWS Amplify is famous for its scalability. So, scalability is no issue. In my organization, about five people are using it.

I have contacted them, especially in the beginning. They are accessible very easily, also via Twitter, and they respond very quickly. So, there was no issue. I would rate them a four out of five.

Positive

For me, it was easy. It was not too complicated. 

The deployment was very fast. It was similar to Ionic. It took a few minutes.

When you're just starting, it is free. You have to pay only when you reach a certain amount of usage. I'm still at the early stage. So, I don't have to pay a lot. At the moment, it is not too expensive for me. It is worth the money.

It is very good. If you already have a small project, you can use it. On the internet, such as on YouTube, there are a lot of short tutorials. You can just follow a tutorial step by step, and then you would get acquainted with AWS Amplify. That's the best way.

I would rate AWS Amplify an eight out of ten. It is still in the early phases, but I see a lot of potential in it.

I am using AWS Amplify for the front end.

The most valuable feature of AWS Amplify is authentication.

AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation.

I have been using AWS Amplify for approximately one year.

AWS Amplify is stable and has good performance.

The scalability of AWS Amplify is good.

We have approximately seven people who use the solution.

We plan to increase the usage of the solution in the future. We are currently using the solution at 70 percent capacity.

The initial setup of AWS Amplify is quick and easy.

I did the deployment of the solution for my company.

My infrastructure team manages the solution.

I rate AWS Amplify a nine out of ten.