Amazon AWS Reviews

We host the service for customer products. Those services are utilized by different product lines, which can be used on AWS.

One of the features offered is scalability on demand.

It's user-friendly.

There are some areas that are not great. For example, with some Microsoft technologies such as .NET, you will have a difficult time deploying it on AWS. It works very well with open-source solutions like Java, but not with .NET technologies.

I would like to see more alerts added to the system. Preemptive alerts would be very good. It is something that happens and you have to do a lot of configuration at that time, which can be complex.

I have been using this solution for ten years.

It's stable and a pretty robust solution.

It's a scalable solution that features scalability on demand, which is working perfectly fine.

We change the core on demand. We can increase the capacity on demand.

We have 10,000 users in our organization who are using this solution.

We have dedicated support. Once we have deployed it, support comes as part of the service because it is incorporated with the solution.

We get all of the support that we need.

The initial setup was definitely complex, but not because of AWS. It is complex because we need to upgrade to be compatible with AWS, which is related to the product and not AWS. The setup of AWS is straightforward.

We deployed it in a cluster way. Initially, it took a week to set everything up.

The first time it took longer, then became straightforward. It only takes a couple of hours now.

Licensing can be purchased on a yearly basis, which is an auto-renewal. We also have an on-demand on-pay purchase.

If, for example, we have provisions for other things and we have a three-peak season then we add more core, more hardware for the on-premises machines. During those periods it is on-demand but the rest of the time it is licensed with a yearly subscription.

The pricing is reasonable.

I would recommend this solution but there are some areas that need improvement. It doesn't integrate well with some technologies and preemptive alerts would be very helpful.

I am happy with this solution, and I would rate Amazon AWS a nine out of ten.

We use Amazon AWS together with MuleSoft's CloudHub, because CloudHub is an extension of Amazon VPC. As part of that, when we set up the infrastructure and everything, we will be interacting with Amazon products. And with big customers, we have data in the private cloud and within that private cloud we have the MuleSoft CloudHub which is connected through the organization's private cloud to a specific geographical AWS public cloud. Regarding security, we also have a number of layers there, too.

As an example, we have seen approximately 300 ETFs developed for different areas, e.g. for United Arab Emirates and other customers. And the internal customers are also using AWS. All in all, there are approximately 10,000+ users who are using it, and things are going pretty well.

The reason I like AWS is that they have a large market share and a large presence. When it comes to our use case, a big positive is that MuleSoft and AWS are working together very well. So instead of competing against each other, they're meshing together.

There have been some issues in the past when it comes to file integrations in AWS's cloud products. However, there are now alternative solutions out there that are helping to integrate them all.

One thing is that sometimes it becomes a problem when troubleshooting our tools because when you have some things local and some things remote on a foreign server, it can get complicated. We find that sometimes it's a challenge to gather the necessary information from logs and such because you need the proper agreement to capture those details. 

In the future, I would like to see Amazon move more into local clouds, by capturing more of the small market. Nowadays, spending a lot of money is not on the list of priorities for many companies, especially considering what's going on in the world. We want to leverage whatever amount is available and still get all the benefits of new AWS cloud offerings.

I have been using Amazon AWS for a couple of years now. 

The infrastructure of AWS is very stable.

AWS is very scalable. 

I've never worked with technical support personally because we have a lot of network engineers to handle that. 

When it comes to pricing, not all applications require that much performance. That's the reason why other cloud markets are also catching up, because the two predominantly high-performance platforms, AWS and GCP, are almost the same.

Looking at the primary market for AWS, I see that there's a lot of customers who have only mid-level performance requirements, because you will have all these normal applications such as online auction websites, gaming applications, voice applications, and so on. These are not, for example, large monitoring applications, financial independents, or brick and mortar companies. So AWS caters to about 40% of the market when it comes to general applications.

As it happens, in many cases, you simply don't need the high-performance offerings from AWS, nor the innovative products from Google Cloud Platform, which can come with large price tags.

Overall, AWS is pretty good and I can definitely recommend it because it's a proven product. When you're solving big problems, you want — first and foremost — proven infrastructure, technology, tools, and mechanisms. Then slowly, you'll be able to remove dependencies by moving to others as needed. So for project initiation and everything, you get to rely on something which is rock solid and proven in the industry with a long track record.

I know AWS can be an expensive option, but it doesn't have to be out of budget if you choose the appropriate level of product for your performance requirements. They can provide high-performance computing resources, while at the same time catering to the mid-level market with lower performance offerings. 

Previously, in the initial days of AWS, back in 2005/2006, there were some concerns about security and such things, but nowadays there is not much to worry about because a lot of those concerns have been taken care of. Recently, there has been another shift in attitude towards them, because not everybody is a big fan of public cloud because of what is happening in the world with respect to data privacy and everything.

Regardless, the three big names of Microsoft, Google, and AWS are really grabbing the market, and IBM is also catching up well. Because of the data privacy concerns, however, I do see some customization in European countries who are interested in interacting with the cloud market at a more local level.

I would rate Amazon AWS an eight out of ten.

We have a financial services application that's a very broad purpose API set. There are rest APIs for executing financial transactions and maintaining financial data. We also have a series of applications built on top of that.

Every aspect of the product is excellent. We have no complaints.

The reporting aspects of the solution are excellent. 

The documentation that is on offer is very good.

The initial setup isn't too complex. A company shouldn't have any problems implementing the solution.

The stability is very, very reliable.

The payment structure is very good.

The scalability is excellent. There aren't really any limitations

The security right now needs improvement. It's not bad, per se. It's just that there's always room for improvement in security.

I'd love to see guarding duties enhanced.

The pricing could be a bit better. It's something that can always be improved upon.

I've been using the solution for years. It's been a while.

The stability is tremendous. There are no bugs or glitches. It doesn't crash or freeze. It's extremely reliable. The performance is excellent.

The scaling is phenomenal. We use a lot of auto-scaling. It's really fantastic. If a company needs to expand, it can do so easily.

In our organization, we have 15 users of the product.

It is very seldom that we have had to contact technical support. That said, when we have, it's been very responsive. We are quite satisfied with the level of service provided. It's been very good overall.

The initial setup is pretty straightforward. It's not too complex. A company that would like to implement it themselves shouldn't have any problems doing so.

The solution is set up as a pay-as-you-go. It's very convenient.

The pricing could always be better, but it's pretty darn good. We're looking into some options for some pricing improvements through some Amazon partners.

There are not any additional costs to the standard licensing fees.

We did look at other clouds, however, ultimately, we chose AWS. We've been extremely happy with it.

We are just a customer and end-user.

I've been an enormous fan of AWS. It does exactly what I need it to do. It would be hard to convince me to use anything else.

I would recommend other potential users to absolutely do it. It cannot be beaten. I'll never run a data center again.

I'd rate the solution nine out of ten. We're very happy with the product overall.

We primarily use the solution for POCs, different experiments, or IoT devices.

The flexibility of the solution is excellent.

The ease of use is great. You can bring something up very easily and tear it back down just as easily. 

Our first system is about to be released. It's our flagship and it's going really well.

The solution scales up extremely well.

They're spinning up and going faster. Anything and everything would you ask for in terms of your feedback they take back and build it and the next thing you know the feature you wanted is available.

The product has a lot of new functionality.

There's always room for improvement, however, they're building out new products. 

The problem with AWS is you have to keep up with the technology. If you don't stay up to date with the technology and its latest changes then you won't know what to use in your infrastructure. For example, as soon as you finish building one thing, then they've already updated to something new. They're always continually updating, rebranding, and rebuilding. 

They tend to oversell before a product is ready.

The solution needs to have more security features continuously added to it.

It would be ideal if they could continue to build a more hybrid collaborative solution - something that allows users to be on-prem, on cloud, or wherever they need to be to build. I'm looking for more AWS to Microsoft (or AWS to Linux) authentication solutions.

There are a lot of management requirements. You need to manage every aspect surrounding the solution, and it can sometimes be a lot.

I've been using the solution for ten years. We've used it over the last 12 months. We have a lot of experience with the solution.

Every system has bugs and glitches, however, for the most part, I haven't had any problems with it. In maybe out of 10 years, I might've seen servers fail three times in my life. Their durability is almost perfect. The stability is excellent. You can rely on their product.

The solution scales up very well. You can easily expand to however big you like. There doesn't seem to be much of a limit. It's very easy to do so as well.

If you scale something up and if you already have your scripts, your JSON, your LAN, and scripts running, and it sees the joint unit, then it brings it right back down. For example, it only uses what you need. If you build in it according to AWS's best practices, then you have a lean mean machine. If you're using their best practices, you'll be fine. 

We are using the solution more for POC purposes, and therefore there are only three people on it currently.

I would them a nine out of ten as a rating. However, the problem we have is not with AWS. Rather, we don't allow them to touch our infrastructure. We've got a lot of security issues and protocols. It's not an AWS issue, it's the way the corporation is built, and that's due to the fact that what we do is highly sensitive.

We would need to ask for specific professional services if we did run into issues.

I have experience with Microsoft as well. 

The difference is that Microsoft is everybody's house and everybody's corporation. AWS is more for if you want to do something new. If you want to just test something new and if you don't have the money, if you just want to learn, you can do something for almost nothing. You can just spin up something and just spin it back down and pay zero. They're moving into what they call this Self-Service Arena now, so then that way you can start building infrastructure. For example, your developers or your designers can actually go in and have a space that they can play in. That's one of the problems that people have with development. People need spaces, where they can go in and build stuff to try.

The initial setup is not complex. It's very straightforward.

The pricing can be very difficult to determine due to the fact that there is so much selection.

We are an AWS customer.

We're using the latest version of the solution. It's always updated, as it's on the cloud and is constantly the latest.

I'd recommend the solution to others. We've been pretty happy with it in general.

I would rate the solution at a nine out of ten due to the fact that they're very flexible. They can be overzealous and challenging at times, however, they really believe religiously in their product, and you can go find many people that know how to use AWS. 

Almost everything is good. It is a whole ecosystem. It is not only the storage, computing, or networking. It is interesting in the way all things are combined to form this ecosystem. It is a very well-built and logical ecosystem that has some small building blocks. These building blocks can be used in the right way to build a much bigger ecosystem that is robust, secure, scalable.

Its interface could be better because there are so many services right now in the product that it is quite difficult to navigate around in this. Its interface could be a subject of improvement.

I have been using this solution for six years.

It has good stability. In six years of working with Amazon AWS, I had only two major incidents, which are very few.

It is very scalable. Our clients are enterprise businesses. There are some customers who put only a part of their business on Amazon AWS, and there are some customers who put everything on Amazon AWS. In some cases, a few applications are going to the cloud, whereas in other cases, everything is going to the cloud, and the migration is huge.

Their technical support is good.

Its initial setup is straightforward. You just need to create an account.

I would recommend this solution. It is a cloud leader, and it is a safe bet. 

I would rate Amazon AWS a nine out of ten.

I am a software developer and I have experience with several languages and technology stacks. Amazon AWS is one of the technologies that I work with. It's integrated with the solution that we have. It's a continuous integration and deployment pipeline.

The most valuable feature is the availability, as we work in different availability zones.

It has been easy to use, and the tools included are quite friendly.

The reliability and ease of use are the benefits.

At times we find ourselves a little trapped, with the lack of customization, for what we need. That doesn't mean that the tool is lacking it means that we are trying to be more creative than the tool and the rest of the market. In cases like this, it is we who need to revise our plans.

I have been working with Amazon AWS for one year.

We are pretty happy with the stability.

The only issue that we have encountered is when Amazon had problems with one of their availability zones that impacted half of the world. We found that we were impacted as well, but it wasn't that difficult for us because we already had a solution with multiple zones. We had a minimal outage, as we were swapping from one server to another. It took less than ten minutes for us, so we were pretty pleased.

It's a scalable solution.

We have both options of vertical and horizontal scalability. Everything that we have needed so far has worked well. We have no complaints.

We are in the process of scaling up. We have an IoT solution and if we translate that to endpoints and devices that are monitored, we would have 70,000 devices, and counting, in the field. In terms of clients, there are 300 to 400, each of them with their own users.

We have contacted technical support and because we are just a small client, rather than a partner, it can take 30 minutes to get a solution. We have not had to use it much to this point, so this may not be a fair evaluation.

This solution was already in place when I started with the company. AWS was in-place and they have never switched to anything else.

Our build, or deployment, is dependent on the application, but the pipeline for submitting a new commit and making it a hot deploy would take from five to twenty minutes, depending on the solution.

For our infrastructure, the cost is approximately $25 per device, and you have to include the other tools that we have in the cloud, for a total of approximately $200,000 per year. Our tools included several databases and Kubernetes. If the price was a little bit cheaper, I would consider this solution to be a ten out of ten.

I'm not very experienced in the solution yet. I don't have a clear view of all that is offered, but with the experience that I do have, I'm pretty happy with the features and it is difficult for me to find where they are lacking.

Currently, I am switching to Redshift, which is one of their solutions that is already deployed. I can't say that I'm missing anything from their roadmap, so far.

I would rate Amazon AWS a nine out of ten.

We are a software company and we use Amazon AWS as part of the solutions that we provide to our clients. The primary use case is an internet banking system. It is used in mobile banking, digital internet banking, and corporate banking.

The most valuable feature is scalability, as it is very easy to scale.

One of the things we are concerned about is the amount of memory because when we deploy the products, we have to make sure that the client has sufficient resources.

It should be easier to monitor the performance and generate analytic information so that we can determine how to provide better support for our clients. I believe that they have a lot of information available, so maybe they can have better analytic reporting.

We have been using Amazon AWS for approximately five years.

We have faced no major issues with AWS. So far, so good, and we plan to continue using it.

Scalability is very good and easy to do.

We have three or four clients using this platform. Most of our clients start with something small, and they are looking for growth. This is one of the reasons that we are using this cloud-based system. It gives them something small to start with, that fits their requirements.

I have seen the email exchange on consulting an issue, and so far, their support is okay.

We did not use another cloud platform prior to AWS.

Installation is not a concern for this product, as it is handled by Amazon.

The only concern is during deployment and integrating with other products. However, there are solutions in place for this and it takes between one and two days to complete.

We have an in-house team for deployment and maintenance, but we also have a consultant to assist us.

This is a subscription-based service and there are licensing fees.

We explored using Microsoft Azure and another cloud, but we did not implement either one. 

In summary, this is definitely a product that I recommend because it's stable. Also, The capabilities and features are better than some of the competitors.

I would rate this solution an eight out of ten.

I am an AWS Certified Solution Architect Associate as well as a Certified Cloud Practitioner, and I am currently pursuing the development specialty. I mainly use AWS to develop cloud solutions for clients.

As a Solution Architect Associate with focus on development, my clients typically ask me to help them personalize AWS services as they pertain to the client's business. For example, I will often work with AWS SQS queues, ETL jobs, APIs and storage, and other services offered by AWS in the cloud.

Generally, my work has more to do with development rather than architecture, and other AWS services that I use include EC2, S3, Lambda, API Gateway, Amazon Connect, Alexa, DynamoDB, ECS, and EKS.

My daily activities are essentially focused around implementing AWS services for clients who want to migrate their existing computing infrastructure to the cloud. For example, if a data center is on-premise, our solution is to bring that data center to the cloud. This kind of migration includes moving all the applications that a company uses to the cloud in progressive steps. We also work to enhance their applications with extra code and the advanced features that the AWS cloud offers, like Lambda for instance. 

The clients that I work with — which include large organizations like universities — also use cloud providers other than AWS, including 3Cloud, Google Cloud Platform, and Microsoft Azure. I, however, specialize only in AWS and Azure.

Here is an example of how AWS has helped one of our clients: With Amazon Connect, we can track all activity in the past and in real-time, so we can know how many calls are in progress and if there are any problems. With a student payment system, for example, if a student has a problem because their credit card was rejected, we're able to trigger an SMS notification to somebody so they can contact the student to make a payment with a different form.

The university is thus able to offer a streamlined payment service with automatic fallback options (e.g. receiving payments with a card reader in person) and all of this is automated thanks to AWS Lambda, which lets us handle customized metrics automatically and in real time.

The AWS feature that I most enjoy is Lambda functions. I primarily use serverless components because they allow you to process things without having to compromise on resources like when running EC2 instances or virtual machines. With minimal effort, you can scale up an unlimited number of processes, even concurrently, to process things. I frequently work with web APIs, so I use Lambda a lot in this area.

Recently we had a long conversation about functionality that is missing in Alexa — in Mexico, specifically. Alexa for Business is a service and platform that Americans can use to make a call to an Amazon Echo device or a telephone via the app. But in Mexico, we are not allowed to use that technology. This is a significant disadvantage of AWS for those living in Mexico.

I also think that Amazon Rekognition could be improved. For example, I have used Rekognition to label things like trucks, buses, etc. Then we put a camera in front of a bus, so that we can send notifications if the bus driver overtakes another car on the wrong side of the road. However, it seems that Rekognition's machine learning doesn't yet have the capabilities needed to make this kind of labeling and recognition system work properly. Thus, we've had to resort to alternative solutions.

And in terms of how easy it is to learn, Amazon doesn't have the most friendly educational platform. It is very obtuse, in fact. I have wasted a lot of time and effort studying through the official channels, so now I mostly use Udemy courses instead. They are very practical and much simpler, but I would still prefer to learn from the official educational platform if it were improved.

I have been using AWS for about five years now. 

The stability of AWS is very good. 

I work with AWS Lambda all the time and I never have any problems with scaling. Recently, Lambda launched a new billing system, which is cost per millisecond. Before, we would get cost per hundred milliseconds, as the minimum, and now if we use only 10 milliseconds, then the cost for 10 milliseconds is exactly how much we have to pay. So that's great, because now I can scale my functions with a precise cost calculation.

I currently have several issues with Amazon Connect because we can only obtain two telephone numbers by default. With this scenario, there was a very difficult process to let Amazon know that we are not working for ourselves in our console, and that we offer our services as a third party, in terms of SaaS and IaaS, to our customers.

I'm not directly involved in the creation of accounts, and I just use them once they are created on the company or client's side. But in Amazon Connect, when we needed to add more users, the time response from Amazon was two or three days. We are subscribed to the developer support plan, and I think two or three days is a lot of time.

Either my company or the clients usually have the console already set up when I start work on it, so there's not much in the way of setup that I can comment on.

With the AWS projects that I lead for clients, it's basically just me that works on deployment, implementation, and maintenance.

When it comes to professional certification in AWS, I implore others to study hard before your exams because $300 is a painful waste of money if you fail.

With AWS products, there is a steep learning curve and I think there are so many aspects because it is really an ecosystem. If you are committed to reducing costs, or increasing performance, or optimizing in any manner, you have to know the solution really well.

I think the best way to achieve this is by experience, but if you don't have any experience, studying hard is the next best thing to do.

The two alternatives I've considered are Microsoft Azure and Google Cloud Platform. However, because I am only certified in AWS, I don't know the difference between, for example, Microsoft functions in Azure and AWS Lambda functions in a commercial sense.

In a technical sense, though, AWS seems to be more comprehensive in the programming languages that it supports. For example, with AWS Lambda functions I can program in Python, PHP, Go, and many others, but with functions in Azure, you are limited to fewer options.

To our client, it's neither here nor there, because they're typically not involved in the actual development, but if you use Azure architecture then you're going to be limited to the programming languages that Microsoft supports.

If you want to take advantage of all the benefits that AWS offers, then it's best to take the time to learn how the entire ecosystem, and each part of it, works. 

I would rate Amazon AWS a nine out of ten.