Amazon AWS Reviews

I use AWS for our insurance portal, managing clients, investments, and other related data.

We use S3, Lambda functions, and EC2 instances for various tasks, including RDR instances.

Its set up is plug and play, so it improves the implementation.

AWS is known for its scalable cloud hosting and computing services. We use various features depending on our needs, including endpoint services, database instances, and EC2 instances.

There is room for improvement in pricing. 

I have been using it for two years.

It's stable. 

I would rate the stability an eight out of ten. Maybe some technology gap, which we don't know is there. 

It's scalable. Currently, around 1500 users are using our application. We might increase the further usage. 

We only contacted customer service and support once. The response was very quick.

Setting it up was easy.

The entire deployment process took us around two to three months. It is a manual process but we plan to automate it with Terraform soon.

We did it in-house. We learned and upgraded our skills ourselves.

We had a team of admins and developers for the deployment process.

It's a bit expensive but stable and easy to use. Licensing fees depend on the contract. It can be monthly or on-demand resources.

AWS is very good to use. Moreover, the integration between various AWS services is very easy. 

Overall, I would rate my experience with AWS a seven out of ten. 

The thing is, in case of disaster, then you really need to think about the disaster, which is less cost-effective. If I'm the customer and I have a midsized environment, I need to host a web application or a front-end application. Why should I go with this on-premises data center, the firewall, the hardware, and then monitoring, then administration? These are more cost-effective. 

So, I will go with the midsized and small-sized public cloud where I can have the opportunity for high availability with the region side. And secondly, in case of disaster, we have the product available without any downtime.

The style, the thoughts, and the people are still not convinced with this public. But they don't have any other options. It has been changed after the pandemic only.

The best thing is scalability.

Some people complain that customization is very difficult in AWS. So they think there are other options. If we have everything ready in AWS or any public cloud, if I have two deployments in bulk, then I will get automation. If automation is ready, then I can do everything in a single click.

In future releases, I would like to see more automation.

I started using this solution after the pandemic. So, it has been three years now. And one thing I have noticed is that after the pandemic, it is more recommended to move to the public cloud. 

Prior to the pandemic, people were thinking of expanding their data strategically with Cisco UCS. They thought in that way. But now the approach has changed.

I used Amazon AWS for a small business, like a midsized business that wants to build their environment in the public cloud. And they want to get high availability, and in case of disaster recovery, they can have other opportunities.

We don't have a much bigger environment. So we have a smaller environment, like 10 to 15 VMs.

For a smaller project in Europe, we deployed Dell VXL for 35 sites. The customer has now invested in Dell VXL and is building 30 to 35 sites for Dell VX-ten. This is a huge investment, so they need to stay on this platform for five years. By the end of their standard support period, their hardware will be end of its life. In the meantime, they are exploring the public cloud to create a hybrid environment. Once their hardware becomes obsolete and offline, they will definitely consider the public cloud. Similarly, people who are still on-premises with legacy or Cisco systems will also consider the public cloud. They are in the existing environment and are just waiting for their hardware to reach the end of life. For the next expansion, they want to move to the cloud.

The initial setup is easy.

In a cloud environment, we need just to associate that business. If I have to build approximately 10 to 15 VMs, we have the templates. We have the AMI. We have everything in place. We need to just automate and place everything in the dashboard. It is very easy to customize.

I will recommend you to use it, at least explore what services they are offering, what features they are offering.  

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

Amazon AWS provides a total solution and helps us to run applications.  

The tool is a hosting platform that we can leverage to open servers. We can use it to build databases. We use cost management and high-performance capabilities of the tool. 

Amazon AWS should integrate AI capabilities. 

I have been using the solution for five to six years. 

Amazon AWS has bugs. It is not a big issue since the product is a SaaS solution and fixes them. 

My company has around 1,000 users who use the product daily. 

I used Microsoft Azure before. I chose Amazon AWS since it has APIs that I can use for software development. 

I rate the product's installation a nine out of ten. One resource is enough to handle the deployment. 

We did the deployment in-house. 

The solution is expensive, and I rate it an eight out of ten. 

I rate the product 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 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 generally EC2 workloads. We use it to host our applications and provide our software service on the cloud. We integrate with EKS (Elastic Kubernetes Service) to manage containerized applications.

EKS helps us manage our containerized applications on AWS. We use various AWS services for different functionalities, such as computing services, database storage, content delivery, etc.

AWS's security model, including IAM or security groups, has contributed to our organization's compliance. It manages authentication, permissions, and overall security posture, which helps us maintain compliance.

AWS has made our lives much easier. It simplifies workload management and operations.  

The cloud-based nature of AWS is crucial for scaling our resources effortlessly. It's a key reason we chose AWS.

We find EKS particularly helpful for its ease of use and management of containerized applications.

Faster API response times and an improved console experience would be better. Enhanced performance across APIs and the console would streamline our workflows.

In future releases, improved compatibility and minimal downtime during upgrades would be significant enhancements.  

I have been using it for seven years. 

I would rate the stability a nine out of ten. It's generally very reliable.

I would rate the scalability a ten out of ten. No problem with scaling this product.

There are around 300 end users in my company using this solution. 

AWS technical support is good in general.  

Positive

The features, quality, and support are likely comparable to other products.

The initial setup is simple. 

Pricing definitely isn't high; I would rate the pricing a five out of ten, with ten being expensive. 

AWS pricing is quite competitive. AWS is cost-effective because it saves time. Faster deployments and testing make it very valuable. Pricing isn't the main thing; it's more about getting things done efficiently. Then, engineers can discover additional savings within AWS itself.

So, it's more flexible. We save a lot of time thanks to AWS

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

It plays a pivotal role in data processing and application development. In our projects, we've harnessed the power of AWS for a range of applications. One key scenario involves building pipelines to process data collected from devices, such as audio and video footage. AWS services like Amazon Kinesis and Lambda functions were used in conjunction with other services like DynamoDB, SNS (Simple Notification Service), and SQS (Simple Queue Service). Another use case involves handling data from e-commerce websites. We collect and process this data using AWS Lambda functions, SNS, and Elasticsearch. The processed data is then fed into a separate application, which serves various marketing and analytical purposes.

The most valuable is ensuring the integrity of our written code through thorough verification. Also, we've leveraged AWS services like Redshift and Glue. Glue, in particular, is a potent tool that simplifies the ETL (Extract, Transform, Load) process. It streamlines tasks like table creation and data loading into Redshift, making the process more efficient and manageable.

There should be improvement in terms of creating databases of varying sizes which would provide flexibility.

I have been working with it for three years.

It offers good stability capabilities. We haven't encountered any issues or downtimes.

In terms of scalability and data security, AWS excels, which is why it's a prominent player in the market.

We receive data from SAP systems, which we process using Databricks. Within Databricks, our coding approach varies; sometimes we use SQL, and in other cases, particularly in certain projects, we employ PySQL and SpotsSQL. We then process this data, which might involve SQL Server, Oracle, or other databases. For ETL (Extract, Transform, Load) processes, we've worked with Data Factory. When dealing with data originating from SAP systems, which often includes unstructured or semi-structured data like JSON, we make use of a diverse toolset. This enables us to load data into databases such as SQL Server and Snowflake or any other required database.

The initial setup was straightforward.

The setup process was facilitated through CI/CD pipelines. Initially, we used the AWS CI/CD pipeline but later transitioned to GitLab because we encountered limitations with certain AWS CI/CD use cases. In GitLab, we found more flexibility, enabling us to execute specific functions or steps independently. In contrast, AWS CI/CD typically follows a more rigid sequence, where phases are executed sequentially from initialization to build and deployment.

The pricing may vary and is often influenced by marketing strategies.

It's a valuable tool, but working with AWS can be challenging. I would rate it nine out of ten.