Amazon AWS Reviews

The use cases of the solution depend on your project. The project I am working on right now is using Amazon Rekognition heavily, along with S3 and EC2. There are a lot of instances involving EC2. The last one involved using a text-to-speech, of which I don't remember the name, but that was the project's main goal. The use cases depend on the circumstance of your project, so it is not the same for all.

The most valuable feature of the solution is that they offer everything around in just one platform. They have almost everything. For example, a couple of weeks ago, I was trying to build a server with RabbitMQ for some kind of real-time communication in an environment where I was working. Amazon already has a service named Amazon MQ, because of which you don't need to configure your server by yourself since you already have it integrated into the ecosystem. It's easy to ensure that the server is there for your system without any issues and allows you to run it in seconds instead of three or four days.

Price is an area with a shortcoming in the solution that has a scope for improvement. Amazon can improve in some areas related to its pricing. Amazon selected the pricing plans, and I had to choose one. In general, it is an expensive tool.

It is cheap when you are starting with the tool since they have this free tier. However, that is not the reality when you really start working with Amazon since you will end up paying a lot at the end of every month.

I have been using Amazon AWS with different clients for six to seven years. I am a customer of the solution.

I believe that it's a stable product. I never had any issues with Amazon. I'm trying to remember, but I think that I have never faced any stability issues. It was working twenty-four hours and seven days a week all the time.

I have contacted Amazon's customer support. It was just a couple of calls when I was working in Iceland on a project, and the servers were not reachable. There was some kind of issue at the country level, not an issue of Amazon specifically. There was some issue with the solution in Iceland.

The initial setup is a thing that you need to learn. The setup part is not easy at all. Usually, in some companies, you have a person that works only with Amazon. You have one profile in your company just to work with the infrastructure services inside Amazon. You need a kind of specialized profile for that work.

The solution's pricing depends on your traffic since they charge you based on the traffic, not the servers. The price can go into many, many thousands depending on the traffic.

The price also depends on your services since, if you are using Amazon Rekognition or S3 with a low tier price.

Well, for a small company, normally, my advice would be that Amazon AWS is not the best option. If you are trying to use Amazon for the first time, it means you need a big project on your hands, and you already have an MVP running. If you are going to use Amazon for the first time, then you already know what you are going to deal with, so such people don't need my advice in that case.

The price is my concern, so I am searching for some other options to leave Amazon. It is not for quality-related reasons.

I rate the overall solution a seven out of ten.

I am impressed with the solution's EC2 EKS. 

The product should reduce carbon emissions. 

I have been working with the solution for ten years. 

I would rate the tool's stability an eight out of ten. 

I would rate the solution's scalability a nine out of ten. 

I would rate the solution's setup an eight out of ten. 

I would rate the product a nine out of ten. 

I use Amazon AWS to host services for my clients, as well as creating SMTP services for them. These are the main two use cases. AWS offers a wide range of services, but I do not use them all.

AWS has a lot of flexibility, which is great.

Recently tried the boot on the desktop, which is where you create a virtual desktop, on a laptop for example. You provide this, and you can use a laptop on the cloud and have everything safe, without having to purchase an expensive laptop.

When I tried with another company, from Azure, which uses the same thing, that with the boot as desktop they had some work needed to make some changes to the AWS desktop. They are not as flexible or powerful as a platform as Azure on this subject.

Previously, they had great VoIP software that they used in AWS, and when I created an account, they didn't have the option to assign too many numbers, local numbers, that could be used for hosting.

In terms of improvement, they should try to give more emphasis to the VoIP system.

I have been working with Amazon AWS for the last two years.

You can deploy and create any number of virtual machines to meet your needs.

Amazon AWS is very stable.

When I'm setting up SMTP servers for clients. They use SMTP as the main platform, but for example, on their CRM, and to be honest, I never go back to that to check for any issues from the day one that I finish the task and provide everything to the CRM developers to proceed with the integration.

We have over 60 companies in our portfolio, and I would estimate that half of them use AWS services.

Going through the chats has left me a little disappointed. It's taking far too long, and I have to come back with questions. The reason could be that they have too many departments internally, so they assign a ticket from one department to another, and it takes a long time to complete the task and provide an accurate solution.

I'm using both Microsoft Azure and AWS at the same time.

I am a Microsoft Azure certified technician, and some of my clients have asked me about some potential within the product. Based on my research, I discovered that this project can be easily designed using AWS rather than Microsoft Azure. This is why I'm learning more about AWS. It is similar to that of Microsoft Azure, and I'm using it, that we can, say, shut down Microsoft Azure completely and then send all of my clients to AWS.

Half of them are AWS, half are Microsoft Azure, and sometimes there are internal IT departments, which need to follow this path, to create the architecture on Microsoft Azure or AWS based on their architecture.

They are difficult to set up. Before you can start using AWS, you must first read the documentation and learn a lot about it.

I would rate the initial setup a three out of five.

It is not very easy, and difficult to complete some of the tasks.

They have a pay-as-you-go subscription. You pay only for the time you use the service. By service, I mean that they are not frequently used by clients. It's the best idea because they are very expensive to them because if it's a small company and you have the option of pay as you go as a solution, it would be less expensive, and better for the company in terms of saving money.

However, if some large clients, for example, use AWS as a hosting provider and compare their prices with other hosting providers, other hosting providers are more affordable. 

I believe that a pay-as-you-go solution is very inexpensive, but not for monthly or fixed prices.

I am a partner and reseller.

I would advise them, before they use the account before they open an account with Amazon, to do their account around just to learn a bit about that solution and then start using it, because it will take a long time to understand how that platform works, how you're going to create a VM on there, how you can create an SMTP.

It is not a simple procedure that we point to and then follows some steps to complete. You must be familiar with information technology. You must have at least basic IT knowledge of a hosting site. This is a platform, and before they begin using it, they must check a number of things and understand how they will proceed.

I would rate Amazon AWS a seven out of ten.

We are using it for certain business applications.

The scalability is a valuable feature. 

The improvement should be done as per business needs. 

I have been using Amazon AWS for five years. 

It is a stable solution. 

It is a scalable solution. Presently, 3,000 users are using the solution. 

The initial setup is straightforward. 

The pricing is expensive. 

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

It is primarily for cloud hosting. If you're developing a solution for a customer who wants it on the cloud, then AWS and Microsoft Azure are two major choices. There are other providers too, but AWS is quite user-friendly.

We use AWS for scalable cloud hosting and computing services. We store all our customer data on Amazon EC2 Instances.

We haven't had any security problems, and Amazon offers automated vulnerability audits. This helps us test our solutions for vulnerabilities and show customers that our systems are secure.

Security, quick deployment, and scalability are the top three features for me.

Like every other customer, I'd suggest pricing is the one feature everyone wants AWS to improve. 

I have been using it for five years. 

It is a stable solution. 

It is a scalable solution. We've worked with about five customers so far. 

We haven't needed technical support.

Sometimes, customers ask for AWS solutions, but we offer choices based on their needs. Price and geographical preferences can influence their decision. Sometimes, the customers can go for a cheaper product.  We don't force them, but we make recommendations.

The quickest way to set it up is the most beneficial feature. We can set up resources quickly and scale them as needed, starting small and growing as requirements increase. That's very helpful. It saves us a lot of time. 

The initial setup is straightforward if you spend some time learning it. They're improving the user interface, which helps.

My team takes care of the implementation. They find it easy to deploy. We haven't faced any issues so far.

It's not very pricey, but it could be cheaper. There are other options like GoDaddy and HostGator.

There are various options, and some can be cheaper than paying a full license.

Read the documentation carefully before starting. Preparation saves time in the long run. For example, the ease of integrating different AWS services depends on your expertise.

Overall, I would rate the solution an eight out of ten. 

We build business applications for our customers using Amazon AWS in 15 different industries.

Many of my customers use many cloud services together.

The most valuable features of Amazon AWS are the high level of capabilities, cloud-native environment, developer-friendly, intuitive interface, and automation. The solution overall is easy to learn from the resources available.

The customization could improve. However, it depends on the customization needed. 

To enhance its capabilities, Amazon AWS should improve its integration with other digital security platforms and solutions, especially those used by companies in domains, such as banking, financial services, and insurance. While Amazon AWS has its own solution, there are many other initial vendor companies that perform exceptionally well. Therefore, it is crucial for Amazon AWS to have better integration with those platforms and solutions, including how to host and integrate them with the rest of the Amazon AWS services. Although Amazon AWS has its strengths, it doesn't always work seamlessly for customers, making it a significant obstacle to migrating applications to Amazon AWS. Rather than focusing on developing new features, Amazon AWS could better serve its customers by supporting these existing solutions in the digital security space.

There are many excellent encryption solutions available, along with many other solutions. By supporting these solutions and offering easy integration, Amazon AWS can create a win-win situation for its customers.

I have been using Amazon AWS for approximately seven years.

When you have complex deployments, such as with more than two availability zones, there are reliability, and resiliency options that are complex to implement and expensive. Providing stability or more complex deployments is possible, but very expensive.

I rate the stability of Amazon AWS a nine out of ten.

We have more than 50,000 users using this solution in my organization. Everyone in our company is using the solution.

The solution is highly scalable.

I rate the scalability of Amazon AWS a ten out of ten.

The support provided by Amazon AWS is highly responsive. We have a strong alliance with Amazon AWS, and we regularly interact with their teams. They conduct knowledge-sharing sessions for us and keep us informed about new features. They are always available to support us. They have helped us from the inception phase of any large engagement up to providing help in troubleshooting some problems. They are extremely helpful.

I rate the support of Amazon AWS a ten out of ten.

Positive

I have worked with Google Cloud Services and Microsoft Azure.

Amazon AWS is known for building many industry platforms, and companies often look to all three hyper scalers to help them build such platforms on Amazon AWS. Large consortia of companies collaborate on such initiatives. However, Google and Azure are more interested in partnering with and supporting industry-level consortiums and technology initiatives, while Amazon AMS sees it more as an engineering capability and expects developers to build everything from the ground up. Therefore, Amazon AMS may need to adjust its approach slightly in comparison to its competitors.

The simplicity of Amazon AWS depends on the engineering processes implemented by the client's organization. Setting up these processes may take some time, but the AWS SDK provided by Amazon is helpful. Moreover, integration with other tooling is also necessary.

Once the processes and platforms are configured, the execution becomes automatic. This has been successfully accomplished in many engagements where pipelines are run for tasks, such as provisioning new infrastructure and making multiple releases.

For a business with a small deployment and with minor features needed the process of implementation can take 30 minutes and in some instances less than 15 minutes. However, if it's a large release with multiple features, including verifications, it can take up to one and a half hours maximum. The more features added the longer the implementation will take.

In comparison to Google Cloud Platform and Microsoft Azure, the database offered by Amazon AWS is relatively expensive. However, the database also offers rich features.

I rate the price of Amazon AWS a six out of ten.

If you compare Amazon AWS with other hyper scalers, such as Microsoft Azure and Google Cloud Platform, Amazon AWS is the most sophisticated cloud development platform.

The amount of people for the maintenance of the solution depends on the engagement we have with our customers. Some of our customers are sophisticated with modern infrastructure and can handle most of the maintenance themself.

The engineering team responsible for development also handles maintenance, upgrades, and support without any differentiation. However, some customers still follow an older mindset, where a separate ops team is responsible for platform maintenance and operations.

One approach is to have a centralized model where a team of 20-30 members manages all the applications, including operations and maintenance. Alternatively, a distributed model may be used, where four or five different teams manage different aspects. However, on average, the team size for the entire IT organization is typically around 20-30 people.

I strongly recommend this solution to others.

I rate Amazon AWS an eight out of ten.

I gave my rating of eight because the price of the feature is more expensive than the competitors.

We deploy our core application and our integrations platform on AWS EC2 instances. Both applications contain multiple containerized Python Django applications, which need to scale with how often and how intensely customers use the platform. 

We need a secure cloud environment to support our new self-service API, allowing customers to hit our services from outside an outside service. AWS provides the security, scalability, and flexibility to make this happen.

We also store large customer files on AWS S3 Buckets.

Without AWS, our organization simply would not exist. Our entire tech stack is served on AWS. Thanks to AWS, we have been able to save money. Thanks to AWS, we have been able to save time and utilize technical resources in other ways. Other ways include building out the front end of our application as well as the back end of our application. Without AWS, we would have to hire network/server engineers, which would take away from our overall speed of growth.

We have found the Elastic Cloud Compute service (EC2) as well as the simple storage solution (S3) to be the most valuable aspects of the solution.

We deploy our core application and our integration platform on AWS EC2 instances. These applications contain multiple containerized Python Django applications, which need to scale up and down dynamically. They also need to be secure to prevent unwanted bad actors from using our AWS compute instances for malicious activity.

Finally, we find the S3 buckets to be quite valuable. S3 allows us to securely store large customer files without fear of them being compromised, changed, lost, or corrupted.

I am not an expert in AWS, nor do I work in the dev-ops department, so I might not be the best person to ask this question. It could be made cheaper. I know we spend a lot of money each month on AWS.

We have been using AWS since the company was founded in 2017 - about five years.

We're a native AWS customer and a provider as well. We have multiple solutions running in there, and we are also doing infrastructure as a code and infrastructure as a service. For example, we can offer you lower prices than the price that you would pay for an AWS instance because we are an official partner of Amazon. So, we are taking all the advantages of what we currently have with AWS. 

It is being used for ECM. In terms of deployment, from an AWS perspective, it is partly self-developed based on Terraform, and we are also using services like S3, S9, and all the things we have in AWS for DNS, but it is highly automated. When a customer comes in and says that they need an instance clustered with certain options and a certain amount of service, it's usually firing up one line of code, and then everything gets set up, including the infrastructure.

We're working with its newer version.

Scalability is one of the biggest benefits we have.

We have a very good approach internally with what we have developed. It involved overcoming some hurdles regarding the single point of truth or single point of configuration, which is sometimes not that easy for AWS. There are dashboards and you have your web service, but bringing all these together and orchestrating is sometimes quite difficult.

My estimate is six years, but it might be way earlier. We ramped up way early with AWS on the market and developed together with them.

It is very scalable. Our customers are from every corner you can imagine. There is no specific type of customers we are serving.

We have a direct relationship with AWS. We are not running with the usual support with AWS. We have other possibilities and are directly integrated. 

It is easy. With our solution, it's really a piece of cake. Even my seven-year-old would be able to set up a cluster with high availability, as long as I tell her what to enter.

It is quite expensive in my very personal opinion. Going on-prem in a data center is, for sure, not as expensive as going to AWS, but when it comes to a point where you are raising and growing, it simply makes a lot of sense to stay in AWS. It is awesome in that way. I am not aware of any extra costs.

Azure is something that we are currently looking into as a second option, but there are no concrete actions planned.

It boils down to two points. The first point would be to have correct planning. You need to know what you want to do and you need to be familiar with what you can do in AWS. The second very important point is that you need very stable and very good monitoring of your AWS instances. This is mandatory because if you fire up a very expensive environment and forget it over weeks, you need to pay for that. I've seen a lot of companies struggling to get an overview of all these AWS machines. It starts by tagging and so on.

I would rate it an eight out of ten.