Amazon EC2 Auto Scaling Reviews

It is used to run applications.

There is room for improvement in the pricing model. 

I have been using this solution for five to ten years now. 

It is a stable solution. 

It is a scalable solution. It is extensively used in our organization. We have over 5,000 users in our organization. 

The initial setup is straightforward. It was pretty quick to deploy the solution. 

The deployment was done in-house. It took only 20 minutes to deploy the solution. We have a CloudFormation template, and we deploy using that.

The pricing model is usage-based. 

I would definitely recommend using the solution. Overall, I would rate the solution a ten out of ten. It is easy to use. 

Amazon EC2 Auto Scaling is a function inside Amazon EC2.

We are using it to scale the capacity of our internet services. It automatically increases capacity when usage surpasses certain thresholds to prevent any issues with capacity.

The solution has greatly reduced our workload. Specifically, it allows us to automate the monitoring of sites, even when we don't have staff available to do it.

The auto-scaling feature is particularly useful. Additionally, CloudWatch and CloudTrail are also important features for us.

As we are transitioning to managing containerized applications, the solution could improve by adding more managed container services as a feature in the solution.

I have been using Amazon EC2 Auto Scaling for approximately eight years.

Amazon EC2 Auto Scaling is highly reliable.

I rate the stability of Amazon EC2 Auto Scaling a ten out of ten.

The solution is scalable.

We have approximately 20 users using the solution. We plan to increase our usage as we progress.

I rate the scalability of Amazon EC2 Auto Scaling a ten out of ten.

We have a very close connection with Amazon. We have all representatives from Amazon contacting us, approximately monthly. We have a channel where we can get in touch with them through instant messaging. 

I rate support from Amazon EC2 Auto Scaling a nine out of ten.

Positive

I use Microsoft Azure prior and Amazon EC2 Auto Scaling. They both operate very similarly. We have a multi-cloud environment and we use both solutions.

The initial setup of Amazon EC2 Auto Scaling is straightforward.

The deployment process is simple and straightforward. It mainly involved configuring the settings on the console. We only need to log in, modified the necessary settings, saved it, and that is it. There were no specific actions required for deployment.

I rate the initial setup of Amazon EC2 Auto Scaling a ten out of ten.

We did the implementation of the solution in-house.

We monitor the spending from dashboards on a daily, weekly, and monthly basis. We have various kinds of dashboards and we have seen a return on investment.

Amazon EC2 Auto Scaling uses a pay-as-you-go pricing model. 

I rate the price of Amazon EC2 Auto Scaling a nine out of ten.

I advise others to establish a baseline measurement of usage and determine the necessary threshold parameters for cost and computing power before implementation. It is a relatively effective and simple way to expand capacity.

I rate Amazon EC2 Auto Scaling a ten out of ten.

We use Amazon EC2 Auto Scaling for SAP workloads to the cloud.

We have found that the sizing in Amazon EC2 Auto Scaling is far off. For example, we will see some at one terabyte and the other one is two terabytes. There is nothing between one and two terabytes. Sometimes it's a struggle if I need one and a half, I still am supposed to pay for two. There are five terabytes, six terabytes, and 12 terabytes, and if I need something at eight or nine, I'm still paying 30 to 40 percent more by taking the one which is 12 terabytes. Microsoft Azure does similar sizes but the gap can be more, such as six terabytes, and the next one is 12 terabytes.

I have been using Amazon EC2 Auto Scaling for the last three years.

We have approximately 1,000 using Amazon EC2 Auto Scaling.

The support from Amazon EC2 Auto Scaling is very good.

Whatever works for the customer, we are more than happy to provide that service. Some of them may need something in a particular region where Amazon AWS is better than Microsoft Azure, we recommend then AWS. If Microsoft Azure is better, then it's Microsoft Azure.

The initial implementation was straightforward. The time it takes for the deployment depends on the environment and components, such as the operating system.

We have a team that does the support for Amazon EC2 Auto Scaling.

I would recommend this solution to others.

I rate Amazon EC2 Auto Scaling a nine out of ten.

We use Amazon EC2 Auto Scaling for our EC2 instances. To run our application platform, we are using EC2 instances. EC2 is nothing but one machine, e.g. it's a remote machine. We are satisfied with the service, and we are especially good at using the service. We are taking clean servers, e.g. our machines run AWS, and we manage everything ourselves.

What could be improved in Amazon EC2 Auto Scaling is its fees. We are looking to have some discounts on billing.

We've been using Amazon EC2 Auto Scaling for almost five years now.

Amazon EC2 Auto Scaling is a stable service.

We find Amazon EC2 Auto Scaling a scalable service.

The first time we set up Amazon EC2 Auto Scaling was not an easy task. We needed a lot of things first, and we needed to learn a lot, but now we are in a stable position in terms of setting up Amazon EC2 Auto Scaling. We can install it immediately.

Amazon EC2 Auto Scaling is not licensed-based. It's server-based. When we want to use more services, we need to pay more. It's a monthly subscription, rather than licensed-based. Pricing or fees for this service could be improved.

On a scale of one to ten, with ten being the best, my rating for Amazon EC2 Auto Scaling is a ten.

We use the solution for two instances for the frontend and backend, then I use CI/CD pipelines to integrate both, and finally, I use Jenkins.

Most of what I've deployed are CI/CD pipelines. AWS is scalable. You can always increase or adjust the resources to meet the specific requirements. I also like choosing an instance in any location, preferably the closest one. We don't have any AWS locations in South Africa, but the latency is about the same as hosting in Europe.

There should be an AWS instance in South Africa, where the latency would be even lower. It might happen soon since AWS has recently opened more data centres in Nigeria. AWS may extend its reach to South Africa, and offer hosted CLI servers there. Most of the problems with AWS are not to do with the solution itself but with configuration. It is something on design, more or less.

I have been using Amazon EC2 Auto Scaling for two years. It is a cloud-based solution.

Amazon EC2 Auto Scaling is stable. We have not experienced any downtime in the past two years.

The solution’s scalability is good. It is pretty straightforward and not in production yet.

The initial setup is straightforward. There is an interface that makes it easy to select what you need, and billing is also quite straightforward.

The front end of the instances takes a couple of minutes.

I set up the solution, but for the database in Postgres, I need to contact a call centre. I need to PRT five times to integrate the front and back end. I also need to work with the consultant.

I first automatically provisioned the required services and configurations. I created an AWS account. I then checked the gigabyte-based deals, reviewed the instance instructions, and added the appropriate insights. This was a good first-time experience, and setting up each instance and naming them was pretty straightforward.

AWS offered some credits, so we have been able to enjoy some of those benefits. The pricing was fair.

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

I use the solution in my personal time. I like to play with it and learn a bit of software.

The solution is very easy to use, and its APIs are also very good.

The product's great, but the pricing could be improved.

I've been working with Amazon EC2 Auto Scaling for a few years.

I rate EC2's stability a ten out of ten.

The workspace is something EC2 has embedded, so it's quite good. They have different options to work with it. I rate the scalability a ten out of ten. I'm the only one using the solution.`

EC2 takes a few minutes to deploy. We have more than one option while deploying the solution. We can use the GUI or the command line, making it possible to use the solution's APIs.

The solution can be implemented in-house with the proper knowledge.

You need some contracts to get support for EC2.

EC2 is a good place to start if you have some good ideas for a business because you can avoid upfront expenses. I believe you can do the same things with Amazon as with Google, Microsoft, or many other companies.

I rate the solution a nine out of ten because you must still learn how to use it first.

We use the solution to autoscale the number of servers per specific business requirements.

The solution allows setting the number of servers required depending on the usage. Later, it automatically increases or decreases the servers per the threshold level.

There should be fewer inputs required that include mandatory details for configuration. It will help someone with less technical knowledge easily set up the system.

I have been using the solution for more than seven years.

The solution is stable. I rate its stability a nine out of ten.

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

The solution has generated over 50-55% ROI for us. It is higher compared to GCP.

The solution is less expensive than Azure and GCP.

I rate the solution a nine out of ten.

We use the tool to deploy NLP modules. 

The tool helps me to process large data sets while scaling up. 

The product's technical support needs to be better. 

I have been using the product for five years. 

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

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

The product is easy to deploy. 

I have seen ROI with the product's use. 

The tool's pricing is good and not expensive. 

I would rate the product an eight out of ten. We plan to increase the tool's usage. You need to have good documentation to start using the product.