Amazon AWS Reviews

I used the solution to build clusters. We use clusters to scale resources. We can process terabytes of data daily in batch jobs and stream processing. I have approximately five terabytes of data daily being processed in batch jobs on the EMR process. We have a script that upscales the services, resources, and runs the whole computation process, and then shuts down the resources when finished. We will also use a flow as a pipeline to build the scripts in sequence. 

Additionally, my company has a lot of fraud detection solutions. We have solutions such as churn prevention, those models are now a product in AWS, and we use them. The resources and services that AWS provides are online 24 hours a day.

There are many valuable features, I find the EMR in the platform easy to use and to learn. The main services that are offered and used most often are easy to use.

Some services that are not used often have poor quality and need to be improved.

The stability is decent with the solution.

The solution is easy to scale the resources.

I rate Amazon AWS an eight out of ten.

• RDS: Because of its auto-scaling, multi-zone availability, and its quick spin up of database servers.
• EC2 Servers: For the agility of server provisioning and the AMI automations.
• Lambda: Because of AI capabilities by writing functions that trigger on events.
• Route 53: For traffic engineering.
• WAF: For security and multiple other features of AWS.

Rolling deployments, quick time to market;

From one day deployment time, it came down to 15 minutes.

Easy provisioning means quick time to market when a new environment is required.

The console's UI could be a little better, a fluid User Experience is missing.

For example, in order to see the instance details properly, we have to scroll the description part up or down, which is not a recommended way of doing it.

Three years.

Just once, when MongoDB infrastructure could not mount to EBS.

No.

Excellent. 10 out of 10 for this.

IBM Softlayer and Azure. Both are not automated to the level that AWS is automated.

Straightforward.

Pay per use.

Yes, RedHat OpenShift.

Migrate to AWS for speed and agility, combined with its security features.

I use this solution to build IoT products.

I am a customer and I have a reselling agreement.

We use this product to build our products and services, which is what we sell.

I like that all of the features are complimentary. I use all of the features together.

It's very user-friendly.

There is nothing that needs changing.

The interface could be improved.

I have been using Amazon AWS for two years.

It is a very stable product.

Amazon is based on scalability. You can scale as you require. We have no issues with scalability.

The technical support is very good.

The initial setup is easy.

I completed the installation myself.

Pricing is good.  It's average.

I also evaluated Microsoft Azure.

I would advise others to use the platform.

I would rate Amazon AWS an eight out of ten.

We had previously been working on a local office server. Our local server wasn't performing well, so we switched to the AWS cloud service. We want to provide smooth service from our application to our end-users.

We first deployed Amazon ASW five or six months ago.

AWS is stable. 

AWS could be more scalable. We have two versions of our product: desktop and cloud. And there are approximately 100 to 200 users there. 

We get our first-line support from our in-house support, and they deal with Amazon support.

I rate Amazon AWS eight out of 10

Elastic Load Balancer: AWS completely manages ELB with less configuration from the users' side. Setting up the load balancer manually is really a headache.

Deploying to the elastic cloud is much easier now with AWS. This makes the go-live process easy.

Billing: They should make billing more simplified. It would be great if they could explain how deploying to elastic cloud is much easier now with AWS. Elastic beans command line interface [eb cli]: You can easily deploy code straight from your code IDE.

The billing calculator has lot of options which confuses the user. If they could provide some template for billing and directly execute those template, that would be great.

For example, the billing template for the standard WordPress Server with Load Balancer and S3 Connectivity: Users could just change the parameters inside the template and execute to see their estimated billing.

We have been using this solution for three years.

I did not encounter any issues with stability.

I did not encounter any issues with scalability.

We were using only AWS.

The setup was straightforward in all ways.

Free tier is always there for demo and testing. Pricing is based on the usage.

We evaluated Microsoft Azure.

AWS is good for any kind of requirements.