Amazon AWS Reviews

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 this solution in our company and for our clients' companies.

I like the IAM, the directory, and the storage.

They should implement the command shell by default. As it is now, to open the console, you have to download the command application. When you compare with GCP, they have the command shell inbuilt.

It would make it more seamless for the administrator to include this. There are times where the machine is not connecting and you can't wait for the RDP because you have to create them quickly.

Building a shell directly from the console is a good solution. This is missing by default. there are ways that it can be done and integrated.

I have been working with Amazon AWS for six years.

Amazon AWS is very stable.

It is a scalable solution, but you can only scale-out. You can't scale up.

We have approximately 200 users in our company who are using it.

Technical support could be improved, they could be better. We don't get SLA with AWS.

They give us a specific time for a solution but they don't advise further. We have to check to see if the issue has been resolved. There should be an automatic email to notify us that the issue has been resolved, by default.

The need to work on proactiveness.

I also work with GCP and with Azure.

The initial setup is easy. It is not complex.

We have a team of 50 people who maintain all of our solutions. It's spread across the team to run 24/7.

The pricing is one of the best in the segment.

They have actually reduced their prices, with the exception of the MLD which has increased.

It's by design itself.

They have placed the pricing well for a reduced market.

I would rate Amazon AWS a seven out of ten.

We use this solution predominately to reduce the amount of effort we need to migrate to the cloud. 

We have had some difficulty figuring out how to monitor how many EC2 instances have been networked into our entire enterprise. We usually try to create a diagram outside of AWS. The types of information we are trying to determine are, for example, what hardware devices are interconnected, and when was the interconnection made.

It is difficult to extrapolate budgeting costs and schedules from the information gathered from the usage of the solution in our systems. We are given a large lump sum of money at the beginning of the year for our budget but it is hard to summarize costs to put down on paper for justification or projections.

I have been using this solution for approximately one year.

This solution is stable and reliable.

We are planning on moving more of our systems to the cloud. Currently, we have approximately 60% of our applications on the cloud.

Our developers found the installation a moderate level of difficulty, there was not anything that was complex. It is helpful to have some tutorials to follow.

The solution is on a pay-as-use pricing model. The price of the solution could always be better but it is priced competitively.

We have evaluated Lambda, and in some cases, it might be a better option than EC2. However, we have decided to go with EC2 because it is closer to a drop-in displacement which works better with our applications, for example, Spring Boot and other similar variations.

My advice to others is EC2 has its specific use case needs like other solutions, such as Lamda. If you have the need for a specific use case this solution could be the right choice. For example, it is possible to have your monolithic application on the cloud and decompose it into your microservice architecture or use it with Lambda capabilities. You can do this and have a high percentage of your application on the cloud. However, you need to be sure it is the right choice, it is something you need to be careful of.

I would recommend this solution to others.

I rate Amazon AWS a seven out of ten.

The most valuable features of Amazon AWS are the EC2 instance for web applications with CDN Networks.

AWS Cloudfront is the official reference for the Global content delivery network (CDN) which significantly reduces latency or slow loading times.

There is a feature called Kinesis, which has to do with image processing. There are a few artificial intelligence tools that Amazon AWS should improve on.

I have been using Amazon AWS for approximately five years.

I have found Amazon AWS to be stable.

Amazon AWS is scalable.

The technical support has been challenging. I have found more tickets are being placed and the availability of the agents has been limited for some of the team members.

We selected Amazon AWS because it was the most mature at the time. It was the initial cloud provider. Then Google and Microsoft also came up with Azure and TensorFlow. TensorFlow is catching up with a few code web programming tools, and that is a point of interest as well as image processing.

In a future release, the solution could improve on the IoT integrations and API access.

The initial setup of Amazon AWS is complex due to how infrastructure is set up in different organizations.

For the initial 12 months, the solution is reasonably priced. On enterprise license contracts where you negotiate, have been reasonable too.

I would encourage the student package for someone who is starting out, they can get acquainted with the interface and the tools available.

I rate Amazon AWS a seven out of ten.

All of our clients look to migrate their workloads to the cloud and we propose the use of AWS depending on the technology of the client or the workload they want to migrate. Our primary use cases are workloadmigrations, infrastructure as a service (IaaS), sometimes platform as a service (PaaS) and software as a service (SaaS). We use different AWS services, Elastic cloud compute, Web application firewall, AWS firewall, LAMBDA, CloudTrail, and others.

AWS has a lot of services that are very good. One of the services I use is AWS Transit Gateway. This service allows me to communicate between different networks in different accounts. It's good for network communication. The other service I use a lot of is "Control Tower", it's a service used to organize the different accounts our clients have.

With regards to improving the service, I don't see any room for improvement at this time. I love the technology, it is a very good public cloud offering with very good services. Until now, there are no services that I don't like.
One other aspect, it would be good to see the basic service level improved with regards to response time. They don't offer 24-hour support. 

I have been using Amazon AWS for around two years.

AWS is very stable. They have an SLA of 99.99%.

AWS is very scalable.

My experience with AWS support is very good. There are four types of support: basic, free, business and premium. It depends on the level of support you have which determines how quickly they can respond about an incident, ticket or request you have. 

It's very easy to set up services in AWS. Depending on the solution you need to deploy it can be very quick. A virtual machine can be deployed in 5 minutes. 

Our company is a partner with Amazon, we implement in-house. 

What is hard with the public cloud service like AWS, is ensuring you maintain a good budget. Plan the monthly consumption properly. If you don't have the expertise in the cloud, your monthly cost can go very high. It's also very easy to set up services in AWS.

I would also suggest companies look for a good partner that has the necessary experience to deploy the services when moving to the cloud. It's very simple, but you need to design a very good architecture for cost optimization and performance.  

The solution is good for integration. It's very flexible and customizable with other services, public, cloud and on-premise.

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. 

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.

We are primarily using the solution as real-time streaming to our data-lake. We also have microservices publishing to APIs. It's a customer 360 application. 

We also used the product for migration from on-prem Hadoop to AWS EMR.

We used to spend about $57,000 on-perm with another solution. Then we lifted and shifted to AWS. It came down in cost to about $33,000 while maintaining the same inner software with Apache Kafka. However, we then got into ECS Fargate, and that brought costs down further to about $22,000. When we removed ECS, we moved into a serverless Lambda for 45 million, and our billing is now $8000 per month. It's an amazing amount of savings.

The solution's API Gateway is very good.

The storage on offer is excellent. 

Recently they improved a lot in the analytics that they have on the backend. 

It's great that the product is completely serverless. 

The implementation for end-to-end, for Lambda serverless implementation, is excellent. I do run about 16 million messages per day with their Lambdas, for my API microservices.

The initial setup is not difficult.

We get a lot of exception errors, and we're working with AWS to figure out how to fix that. when we lift and shift . We get a lot of alerts. 

As our serverless Lambda is maintained by AWS, in a certain aspect,  we need to gain some more visibility into what is going on when problem happens with AWS serverless 

Their metadata management in AWS needs improvement. They need a centralized metadata management tool, where it can be integrated with  outside metadata tools  with the API. We really need a central metadata framework.

I've been using the solution for four years. It's been a while at this point.

The stability of the solution is very good. there are no bugs or glitches. it doesn't crash or freeze. It's reliable. That said, initially, we did have a few problems, however, everything has ironed out. It's great now.

Scalability-wise, the product is very good. The Lambdas and the serverless architecture are very good on AWS. If a company needs to expand, it can do so with ease.

We have a lot of APIs, and we'll run them on my customer 360. There are six departments that use the product. We have about 1,000 users currently.

We've dealt with technical support in the past and have not been satisfied for the most part. Azure's technical support is much better. AWS often can't help us resolve our issues. But they brought some good consultants basing on our request and helped us . The account Manager always there when he took over this account .  

 i recommend IAAS AWS , for IPAAS ( integration as platform service) and Hybrid cloud Azure

We've also planed for  Azure. We've found Azure to be much more helpful when dealing with issues than AWS has been. I prefer them over AWS in support , application development  and integration as platform. But AWS has great products like S3 , API gateway , transit gateways , route 53 . AWS has  more OS options than AZURE and database offerings. their EMR is good with spark and python but not well supported for Scala and HBase. AWS serverless offerings are very good with out any major problems which includes ECS with fargate and EKS . But we got a good support from account manager

The initial setup is not complex. When we lifted and shifted faced lot of problems on EMR. Moved to ECS, as well as serverless Lambda, it's was that difficult then. That said, we had to think about how we run our Lambdas, and what problems we are facing or might face.

We're also facing a few problems due to the fact that we use encryption, HCM. When we initially started loading this data, batch data, a lot of Lambdas came, and our limit in HCM is only about 5,000 a minute, however, it quickly jumped up to 20,000 which made it so that we could not load, and errors came up. We had to turn to AWS to get assistance. We just ask them if we can have space over a few days for 20,000 and then they scale it back to 3,000. they helped us 

In terms of the implementation strategy, ours took about eight months. The lift and shift happened within 3 months. Then, we took another four months as we had a lot of problems with our scale-up programming due to multiple issues - for example, libraries, EMR, AWS doesn't have. We faced some problems when we had to change our code according to AWS, or we have to bring in those libraries on our own. So that's where it took time, maybe four months.

For ECS, it took about 30 days to move everything we needed to. 

We don't have a lot of staff to maintain the product. We have about eight people who are capable of doing so. For example, we have someone on infrastructure, who is an architect and we have an enterprise architecture team. I have four developers, two for API and two for Lambda, and one is a systems admin. 

Initial setup environment helped by AWS free . We were able to handle every aspect of the implementation in-house. We didn't need any consultants or integrators. We used our systems manager so that all of our deployments - including environments and keys - can be stored on our SSM. A lot was automated as well.

excellent in covid -19 situation . 

We saw a lot of cost savings when we switched over to AWS. It can really save a company a lot of money.

Azure and AWS 

I'm a user and  implementer.

The solution is on the cloud; it's always the latest version. It's constantly being updated, and we're always using the latest version.

We use both public and hybrid clouds as deployment models.

I'd rate the solution at a seven out of ten.