Amazon AWS Reviews

You can design and customize solutions with AWS. It has so many options, including storage, computing, database, notification, and messaging solutions. It depends on what the application team designs. 

I like AWS for its scalability, reliability, and availability, and it's much more mature and user-friendly compared to some other cloud providers. The learning curve and time for deployment are also shorter.

Amazon needs to develop better tools for troubleshooting network traffic, application insights, performance, and even some aspects of integration mapping. I'm hoping AWS implements something like Azure's Network Watcher and a log analytics solution where a can pull logs from various services and present them in a single dashboard. I want to summarize the performance and usage of every service and application.

All cloud solutions are scalable. It depends on the design, but most of them scale well. There are tens of thousands of users working on the solution.

Amazon technical support is great.

Deploying AWS could be straightforward or complicated depending on the use case. If it's a simple application, you can deploy it within a day. If it's very complex and your team isn't experienced, it can take months.

The amount of maintenance needed depends on your application and how you define support and maintenance. Some staff will handle things internally and others will be responsible for the cloud applications. 

I would say AWS is balanced. Cloud solutions are not cheap, and the ROI could vary widely according to your usage.

The cost depends on the usage and applications. If you're hosting thousands of applications, you'll be paying tens of thousands of dollars. In addition to usage fees, you have to factor in the costs of development teams and the staff you need to support the applications. These are the three costs you need to kind of calculate to decide on the budget.

I would rate AWS 7.5 out of 10. There are a lot of options in this space, and Microsoft is also good. We are evaluating the data on each. We would rate Azure close to eight, so they're both great solutions. 

My primary use case of AWS is cloud computing. I have been using the EKS, EFS, S3, and Lambda. I have a lot of experience with the Kubernetes cluster service, as well as AWS, Azure, and GCP. 

This solution is cloud-based. 

Amazon AWS has many merits, in terms of scalability, stability, and availability. I have loved using this tool. 

Amazon AWS could be improved with cheaper licensing costs. 

I have been using Amazon AWS for more than four years. 

This solution is stable. 

This solution is scalable. 

In my organization, there are approximately 500 to 1,000 users of Amazon AWS. 

Amazon's technical support is excellent. I am very satisfied with their support. 

The initial setup was very simple. I have been using Terraform as an infrastructure as code tool, and with Terraform, it's very simple. Within one day, I can provision the AWS Infrastructure as a Service tool and install our platform based on the cloud and data analytics. 

From a cost perspective, Amazon AWS is excellent. You need to pay for a license to use AWS, and the license could be cheaper, but in each of the cases and instances I've used AWS, there has been a good chance to save money. 

I rate Amazon AWS a ten out of ten. I usually recommend AWS because I have loved using this tool. Most of the time, I recommend it as a real-time information and patching service with Lambda. 

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.

It's a powerful infrastructure as a service solution, IaaS. It offers compute resources, storage, networking, and databases to quickly create your cloud infrastructure.

Apart from the infrastructure as a service, the AWS Lambda, which functions as the service FaaS, is really powerful. 

It's a powerful way of quickly assembling or developing applications, which can be scaled immensely and also at a fraction of the cost because you are charged per the execution time of each function. If you are writing a small function as an AWS Lambda function, then you are paying only for those milliseconds for the time at which it runs. 

It's a very cost-efficient way of running applications in the cloud rather than running an EC2-compute instance, which is charged by the hour or by the minute. You typically have to keep the EC2 instance updating all of the time. Whereas in functions, a function is invoked only when a user is calling it. Or, the front-end is calling the backend function. Lambda is very powerful and it is also typically used as a mobile backend. Essentially, it's a very strong API-based backend for mobile solutions.

It has many choices of computer options, storage options, and even database options.

It's flexible, you can run any kind of workload on the infrastructure.

One feature I would like to see is to have a better or a more user-friendly web console. 

The web console of AWS is not so user-friendly. They can make it more user-friendly, which will be good for administrators or users of AWS.

I have been using Amazon AWS for five years.

We are using the latest version.

It's very stable. It is highly reliable.

It is highly scalable. It's a very powerful platform.

In my previous organization, there were 12 people using AWS.

We have used technical support to an extent, and it's fine. We are satisfied with technical support.

I have used Azure Cloud, Oracle Cloud, and I have a bit of experience with Google Cloud as well.

You have to create an EC2 instance, which is the compute. We have to create that to get the compute platform, but you have to install your application. You have to patch the operating system and you have to upgrade your operating system.

The operating system and upwards is the customer's responsibility in an EC2 instance.

It's a straightforward installation because it's your application and your operating system just like you are on-premises, but you will do it on the cloud through a browser or through a CLI, a command-line tool.

The deployment timeline depends on how complex your application is. Because you are getting the platform from AWS as a computing platform, you have to install your application. It depends on the complexity of your application, so it varies.

Depending on how much you are using it, determines the maintenance. Typically, you will need different roles, you will need administrators who operate this environment, and if you are also developing applications, you would need developers.

The installation and deployment can be done by yourself.

You are not paying a licensing fee, you pay for consumption. You pay for your consumption and it' is typically paid on a monthly basis.

It's a pay-as-you-go model.

Some services are expensive, but the basic infrastructure services are a platform that is reasonably priced.

We plan to continue using this solution, and I would definitely recommend this solution to others who are interested in using it.

I would rate Amazon AWS an eight out of ten.

I use the solution in my company to use several services like ECS, EKS, and S3 while also making it easy to use its hosting services in our infrastructure. The solution is good for efficiently leveraging all the aforementioned services to host different products.

The cost of the product is an area of concern where improvements are required.

I have been using Amazon AWS for around six years.

The solution's stability is good. Stability-wise, I rate the solution an eight out of ten.

The product's scalability is good.

All the people in my company use the product. My company has engineers, software developers, site reliability engineers, and DevOps engineers who use the product.

The solution is used on a daily basis in my company.

For the purpose of scaling our company's operations, we host most of our applications on Amazon EKS. My company uses third-party open-source solutions for scalability purposes, so we are not completely dependent on Amazon AWS for autoscaling.

My company takes care of the problems related to the product. My company doesn't contact the product's technical support team. Though I have some previous experience with the product's support team, I haven't recently contacted them.

Previously, I worked with a tool on an on-premises model. I chose Amazon AWS since I wanted to use a cloud-based product.

My company is not dependent on Amazon AWS for deployment purposes since we use our own tools to handle the deployment area. My company uses Amazon AWS for the underlying platform but not for the deployment area since we have our own setup for it.

The initial setup phase may be pretty easy for those who learn to gain knowledge and expertise in Amazon AWS. At the initial stage, the product's users may look for more documentation on the tool, but I feel that the services under Amazon AWS are self-explanatory. I rate the product's initial setup phase a seven or eight out of ten.

I am a part of the team in my company that carries out the product's deployment in multiple regions.

The product's deployment process consists of a fully automated setup phase. Though my company had to be involved in a lot of engineering work in the initial phases, only around four to six members were required to take care of the deployment after the automation.

The solution can be deployed in around 10 to 15 minutes.

The tool is expensive.

As of now, our company does not need to leverage Amazon AWS for Amazon Big Data Analytics or Amazon Machine Learning. In the future, Amazon AWS can be used to leverage the benefits of Amazon Big Data Analytics or Amazon Machine Learning. Presently, my company plans to stick with the microservices model.

There is no need to maintain the product from our company's end since Amazon AWS takes care of the maintenance of the services the tool covers.

For cost saving, shut down instances when not in use and use spot instances while implementing step scaling policies. Doing regular audits, you will get to know what resources in your environment are leading to cost consumption.

AWS Global Cloud Infrastructure does not directly impact our company's application performance and availability. My company just consumes the services covered under Amazon AWS, after which we plan our application architecture. The impact is felt if Amazon removes support for some of its global products, as it may impact some legacy applications, but my company does not face many issues since we mostly upgrade such applications.

I rate the overall tool a seven or eight out of ten.

The product is easy to use. Its availability and support are its biggest strengths.

IAM must be made simple and straightforward. It is a little bit complicated compared to GCP.

I have been using the solution for three to four years.

The product is stable.

The product is scalable.

My company had signed up for professional support. We did not have any issues with support. It would be really tough to reach out to the support team on a personal level. For personal users, I rate the support a three to four out of ten. For professional users, I rate it a nine out of ten.

We are also using Google Cloud Platform. The choice of the product depends on people’s familiarity and their inclination toward using a certain product.

The tool’s pricing is reasonable.

I would recommend the solution. Overall, I rate the product a ten out of ten.

The introduction of the ITD pipeline makes the development and operation cycle easier for the organization.

The solution also helps organizations to move applications to a containerized platform.

Instead of using some third-party solutions, Amazon should include them as part of its offering.

Currently, we are using some third-party services for various purposes. Amazon can acquire those open-source products and provide them with managed services.

I have been using Amazon AWS for about six years.

I rate Amazon AWS an eight out of ten for stability.

The solution's scalability is always high, and the customer can seamlessly scale up the solution. I rate Amazon AWS an eight out of ten for scalability.

The solution’s technical support is good.

Positive

The solution’s initial setup is very easy. Amazon AWS is the easiest cloud platform to learn and deal with compared to any other provider.

I rate Amazon AWS a nine out of ten for ease of initial setup.

Any service built on AWS is very easy and quick to deploy and does not take much time. Within 10 to 15 minutes, you can bring a server up and launch a website.

The pricing of Amazon AWS is high compared to any other cloud provider.

Amazon AWS was deployed on the cloud in my organization.

Overall, I rate Amazon AWS an eight out of ten.