Amazon AWS Reviews

I've used it to create some internal projects for my organization, particularly for designing the infrastructure of those projects.

One feature I find most valuable is the easy deployment by using the channel model for  serverless architecture. Another feature I find valuable is the versatility of the service S3 because it allows you to give permissions to describe the users from their own accounts, from external users, or external accounts.

On the console, they used to have some shortcuts making this solution easier to work with, but now we have been dealing with so many problems on the console, and some of the options are not very useful in my perspective, so they should bring back those options that make things easier to run some of the services.

Most of the time the options are pre-selected, or you have to go with the default settings, but from my perspective, there are some services which are now more complicated to use than before.

An additional feature I'd like to see in the future is more integration with public repositories, though some use their own repositories for security purposes, but I think it'll be easier to deploy services through public repositories.

I've been using this solution for almost four years now.

This solution is stable. I've been using it for a long time and have only seen an outage in one of the regions. It's a good solution.

The scalability of this solution is good.

The technical support of AWS is very good. When I need something, they reach out to me fast.

The initial setup was straightforward. The complexity of the setup will depend on the number of services e.g. it's something that involves a lot of services, it could get complex, but for a complex setup, you could use things like transformation or Terraform because they will enable you to use infrastructure as a code to make it easier. There's a lot of things to configure.

Licensing of this solution is paid on a yearly basis.

I evaluated Microsoft Azure.

This was deployed on the cloud. I don't remember which version because I didn't deploy it. I was not the person running the project of implementing AWS, but I know the client used it, but I don't know which version.

It's not so difficult to use because there's a lot of tutorials.

I'm not completely sure about the number of AWS users in our organization. We have a partnership with them so we have some accounts, but we don't completely have our load on AWS. We are mostly on Azure. Our main server is on Azure. On AWS, we mostly have some internal projects and services, but most of the main load is on Azure.

We have a small workload on AWS. Sometimes we use it to deploy some of our best projects. We use it on some internal projects. It's a random thing so it could be 1,000 users or 50 users. I'll say approximately 200 to 500 users.

We don't require too many people for deploying this solution because our projects are proof of concepts. Up to ten people from different departments would be needed for deployment if it's a business requirement e.g. people from Approvals and Projects, etc.

As for increasing AWS usage, the organization sometimes thinks of moving some of the load to AWS because of good pricing, because currently, our main streams are on Azure, but it's not a sure thing.

I'm unsure if there's any additional cost aside from the need to pay the license annually because I don't directly manage it.

My advice to organizations looking into implementing AWS, especially if they're going to use it on a big scale, is to take advantage of AWS' organization model to make integration with their policies easier. It will also make administration easier for the different accounts, departments, and structure of the organizations thinking of moving to AWS.

I would rate this solution a nine out of ten.

My primary use case was as a place to migrate legacy systems.

AWS has reduced our costs and maintenance requirements. It also allows us to control our load in peak times and automatically increases or decreases your capacity as required. 

The features I have found most valuable are S3 buckets and Lambda services.

An area for improvement would be API creation - a lot of tools are provided, but there can be issues with integrating them. There is also a cost underlay, in that at the end of the day, some costs are not in the picture, so AWS needs to improve its costing toolset.

I have been using this solution for two years.

The stability of AWS has improved over time and can now be well managed.

This solution is scalable to any limit.

I previously used Rackspace Openstack but switched because it required more manpower than AWS, and AWS is more cost-effective and tolerant.

The setup was somewhat complex. It was done in three phases over a year.

This solution reduced our overhead cost by 30-40%.

Technical support is expensive to use.

I evaluated Oracle Cloud, but it was more complex to use and provided a smaller toolset than AWS.

This solution is one of the top tools available for legacy migration. I would rate this solution as eight out of ten.

We are using the solution for our core applications and our core infrastructure.

The product offers a lot of functionality. 

Our vendor who provides us a specific core application uses AWS and it's just simple for us if we use it too. 

The initial setup is straightforward.

The solution has been issue-free. It's very stable and the performance is good.

The solution can get to be a little expensive. 

I've been using the solution for a year and a half. 

The product is stable. There are no bugs or glitches. The performance is good.

We have about 100 users on the solution right now. 

Technical support is good. We have had no issues with them. We are satisfied with their service.

We also use Microsoft Azure. 

The initial implementation process is pretty simple and easy. It's not complex or overly difficult. A company shouldn't have any issues with the deployment process. 

The costs could always be lowered.

How often we pay can vary, depending on the exact service. We pay, for example, both yearly and monthly.

As a cloud-based solution, we are using the latest version all the time. 

I'd rate the solution at an eight out of ten. 

I would recommend the solution to other users and organizations. 

I use the solution for deploying some applications that use cloud computing.

It offers a lot of tools, which we leverage. 

At the moment I'm using Lambda service and also AC2 machines - as a platform as a service and infrastructure as a service.

The pricing model is good. It's pay-as-you-go. You only pay for what you use. 

The solution offers a lot of very helpful documentation. There's also a great community that surrounds it that is quite helpful if you have questions or want to learn something. 

Personally, I need to improve myself in terms of the knowledge I have around the product. My goal is to maybe get certified in order to understand it better. It would be helpful if they would be able to provide me with more certification information. 

It's a good platform. I don't have any issues with it at the moment. 

It would be ideal if they could provide automatic health reports. That way, I would be able to understand at a glance the state of my services at any given time. 

I've used the solution for three or four years at this point. 

The solution is stable. We have many items deployed in AWS and we haven't had any issues. there are no bugs or glitches. It's problem-free.

AWS provides us with a lot of tools for deploying automatically when we are working, for example, in a new feature. We have options for automatic deployments and don't have issues with size.

There's a lot of great documentation and community support. I'm learning a lot and can find any answers I need there. 

I'm working with AWS, Azure, and Google Cloud Computing right now.

I work with my customer's solutions and I deploy into AWS to provide the end product for my customers. I don't directly deal with AWS implementations themselves. 

The pricing is good and it's set up as a pay-as-you-go. It's not overly expensive. 

I'm just a customer and an end-user.

I'd highly recommend the solution to other users. It's one of the best cloud options out there right now. 

I'd rate the solution at an eight out of ten.

This solution has many use cases. Amazon AWS offers a lot of services, all of which are useful. How useful this solution will be for you depends on how it fits your business. 

Amazon AWS is easy to use and in the past two years, I've never had any issues with scalability or stability. 

This solution could be improved by a better licensing model, especially for third-party software. Amazon AWS could also potentially be improved by more free storage, but I think that it's okay when compared to competitors' products. 

I have been using Amazon AWS for more than two or three years. 

This solution is stable. I haven't had any problems with stability in the past two years. 

This solution is cloud-based, so it's scalable. It is elastic, so as soon as you want to increase storage, you do so without any issues. There are about four thousand to five thousand people using AWS in my organization. 

I have contacted Amazon's technical support and it was quite an easy process. You will have a solution within 24 hours. 

I didn't use another fast cloud solution before Amazon AWS. 

The initial setup is easy and you don't really need to install anything. If you understand cloud solutions, you can easily do it yourself. 

I implemented myself, with an in-house team. 

We need to pay for everything. If someone is a personal user, they get one year free. But if you are using this as a professional or enterprise solution, then your company has to pay. The license pricing is comparable to that of competitors'. 

I rate Amazon AWS a nine out of ten, primarily because I have a background in Java. Someone else with more experience in Microsoft technologies would probably prefer Azure. I recommend AWS to anyone considering implementing it because it's easy to use. 

I am using it for enterprise warehousing. I am using it for web development, data warehousing, and also for building apps.

I am using its latest version. In terms of deployment, it is a platform as a service.

Macie is great. It is a service that makes recommendations on a data layer for cybersecurity. It is a great service.

Its elasticity is good, and I haven't come across any problems with it. So far, everything has been good.

One thing that Azure offers that I think is good is Migrate appliance. So, Azure has a migrate appliance that allows you to run against workloads to determine the cost, preparedness, and scalability. I haven't found a similar feature in AWS. That kind of service would be great on AWS too if you could point it to the data center.

I have been using this solution for well over five years.

I have not had any performance issues.

It's very easy to scale. Its elasticity is good. If you want to scale up or down, you can. You can scale out. There is no problem at all. That's one of the features that I like about it.

We have less than 50 people who are using this solution.

I've not used their tech support yet.

We didn't use a different solution previously. They're the first.

You need to know what you're doing. I know they're trying to make it easy. Some things are easy. Some things you have to know what you're doing.

It seems to be reasonable. It's the first one that I've used as a cloud platform, so they've set the benchmark for me, and now, I'm comparing everything else to them.

I would advise others to just plan out what they are looking for in terms of use cases. 

I would rate Amazon AWS an eight out of 10.

We use it to host our e-learning platform.

AWS is a platform, wherein they give you a virtual instance of a server. So there is no version per se. They just give you a virtual server. The other software we use is free. We use it for conducting our exams and everything. We use a free, open source software, which is not a commercial software.

Remember, this is a plain vanilla platform. So we don't have to do any actual investment in servers and other things. That is the general advantage of cloud that everybody gets. You don't have to pay a lot of money. And at any point, if you feel you don't want to use it, you stop. It is as simple as that.

The features that I have found most valuable are their compute and their Relational Database Service.

The features that should be improved are that there should be better clarity on their invoicing. There are so many things they charge for - high line items in the invoice. I think there should be more clarity and more ease of use with their billing.

I'd like to see better ease of use with the billing console and a clear dashboard to understand the usage.

I have been using Amazon AWS for almost three years. We are continually using it.

Amazon AWS is very, very stable.

No maintenance is required.

Scalability is unlimited. From one to 10, it is 10.

We use it, but our training participants access it. A lot of people access it. In a year, at different points in time, 200 people might be using it.

I don't think we will be expanding usage because we purchased a little more than what we needed. We don't need to spend any money now. We only pay our monthly charges.

Technical support is good. If you raise a ticket, they're very good. Even with billing, if you have some issues they take care of it. If you are overbilled or you're not using it and then you turn one thing by mistake, and all of a sudden the bill has increased - they'll take care of it.

Previously, we were using general hosting, they even call it shared hosting. But it was not scalable and it was not fast.

The initial setup is all easy. It's very easy.

Our deployment took just a few clicks. You are talking seconds.

I had our technical team do it. But you need a technical person. It's not that anybody can do it or a person like me can do it. You need to have a technical person doing it.

We have seen a return of investment with Amazon AWS.

We are just a customer. We just pay monthly for the subscription cost. I mean, hardly $50. We are a very small company. 

My advice to anyone considering Amazon AWS is that they should plan properly for their spending and they should have good control over their technology team. Otherwise, if the technology team doesn't know enough and they keep on creating more services, you'll be surprised with the invoice. Technology and finance should work very, very closely in the cloud.

On a scale of one to 10, I give Amazon AWS a 10. It's a really good product.

We use Amazon AWS for provisioning and the majority of our deployments.

We support and provide services for our clients who lean towards using AWS.

Amazon AWS is easy to use.

It scales well and is flexible.

When compared to Google Cloud Platform or Microsoft Azure, it has almost all of the features.

As a result of the competency, I believe that most people are now leaning toward Azure rather than AWS. That is also according to Gartner's forecast, more people are turning to Microsoft Azure.

The price could be better.

We have been using Amazon AWS for more than three years.

We are always using the latest version.

Amazon AWS is a stable solution.

It is a scalable product.

When the number of users increases, the bandwidth automatically increases, and when the number of users decreases, the bandwidth decreases.

We have a large organization with over 3,500 users, and more than 60 customers.

Our organization has an AWS center of excellence that increases our usage.

I personally have not contacted technical support. 

We contact our own center of excellence team, who would then contact the AWS support team for any information we required. That is the order in which we must proceed. It's the hierarchy that we must adhere to.

I am also, familiar with Splunk.

The initial setup is straightforward.

The installation is done through the AWS Cloud and is so simple that it only took me 15 minutes to create instances, possibly even less than 10 minutes.

We have 200 engineers who are responsible for both the development tasks and the maintenance.

I was able to complete the installation myself.

When compared to GCP, Google, or Azure, the price could be lower.

As a company and a platinum sponsor, we know exactly where management will make a decision on getting the best price for us.

A monthly fee is a good option for a startup company or an individual, and it is paid yearly for larger organizations.

I would recommend this solution to others because I am not familiar with Azure and only have experience with AWS.

We don't have any issues with this product. I would rate Amazon AWS a ten out of ten.