Amazon EC2 Auto Scaling Reviews

We have EC2-based architectures. We deploy our applications on EC2. We also use Amazon RDS.

The operating system, Amazon Linux, is valuable. We like it very much. The availability of the instance is valuable. The documentation is good. We can use Systems Manager to manage nodes and Patch Manager to manage patches. The solution provides a variety of features.

The tool must provide proper guidelines to troubleshoot connectivity issues. It must also improve AMI creation.

I have been using the solution for the last four years.

The product’s stability is perfect. I rate the stability a ten out of ten.

I rate the product’s scalability a ten out of ten. It is made for scalability. We have 20 users. We are planning to increase usage.

The support is good.

The tool is very easy to deploy. I like the new interface. The time taken for deployment depends on our requirements. It is a cloud-based tool. Sometimes, we use the CloudFormation template. Sometimes, we do it manually. Generally, it takes around five minutes. We create CloudFormation stacks to deploy the tool depending on the type of instance we require. We need more than ten technical team members to deploy and maintain the solution.

We deployed the solution ourselves using the documentation.

The availability is valuable. It is very useful to deploy the instances automatically.

The solution is not expensive.

The product is very helpful. It has various features that we can utilize. Overall, I rate the product a ten out of ten.

The product helps our organization minimize costs by providing high availability of applications and microservice.

The product's most valuable features are high availability and persistence.

The product should improve vertical scaling features. It should support scaling inside the nodes. It requires the capacity to scale microservices in other nodes.

We have been using Amazon EC2 Auto Scaling for seven years.

I rate the platform's stability an eight or nine out of ten.

Compared to the product, Karpenter has a high algorithm to manage horizontal and vertical scaling. I rate its scalability a six out of ten. 

We used OpenShift earlier. We switched to Amazon EC2 Auto Scaling for better infrastructure performance.

The initial setup process is easy. It involves configuring a cluster, creating a cluster request, and using code to deploy it. The deployment time depends on specific applications and infrastructure. It takes approximately three days to complete and needs one person to execute maintenance and patching.

Sometimes, we take the help of an integrator, whereas sometimes, we refer to the documentation for the product implementation.

The product's pricing depends on the traffic and workload. Additional costs exist if you use services like CloudWatch, VPN, etc.

The product is easy to use and configure for small nodes. For large nodes, I advise others to use other solutions like Karpenter.

I rate Amazon EC2 Auto Scaling an eight out of ten.

I use the solution for development, production, and testing.

The product is flexible. We can get whatever we want in a minute.

Automation is very hard.

I have been using the solution for two years. I am using the latest version of the solution.

The stability is very good.

The tool’s scalability is great. Around 20 to 30 users are using the solution in our organization. It is an enterprise solution.

Previously, we used an on-premise solution.

The initial setup was okay. The documentation was great. The time taken for deployment depends on whether we want automation. If we want automation, the whole process can take a couple of weeks to set up all the automation.

We deployed the product ourselves. The deployment process is very well documented in Amazon.

The ROI is good.

The product is quite expensive. We pay for the license yearly.

I would recommend using the product and automating everything from the beginning. Overall, I rate the solution an eight or nine out of ten. We seek support from solution architects for design.

I use the product for its availability and scalability features.

The solution is highly scalable. If one of the instances has some issue and the server is terminated, or if the production is running on a server and it gets shut down, we would not have any backup plan. We will have to recreate another server and run production. The product helps us by creating another server automatically within a minimum amount of time. This process decreases the impact on production and downtime. The product fulfills all my requirements.

The existing instance should not be terminated during scale in and scale out. The product does not explain why a particular instance is terminated. There is no option to check the log either.

I have been using the solution for two years.

We have not found any bug in the solution in the last two years.

The product is stable. Around 100 people use the product in our organization.

We can easily deploy the product if we have the documentation. The document is good enough.

The product is cheap.

The solution is cloud-based. If one of our CPUs or memory has an issue or is being utilized more than usual, another instance scales up automatically. Overall, I rate the product a nine out of ten.

Our use case is for when there's a need for additional processing capacity. Broadly speaking, the platform has inbuilt intelligence that detects a high workload, and then automatically scales out to accommodate the increased demand for capacity. We have production systems that run 24/7.

It's the auto-scaling that is the main valuable feature. 

I'd like to see more integration with products like Ansible and other platforms. 

The solution is very stable. 

The main feature of this product is scaling. The product itself does not need to be scalable. 

The technical support is good, they respond quickly. 

The initial setup is straightforward and AWS provides good documentation which can be easily leveraged by anyone trying to use it. Deployment takes a maximum of an hour. It's just a matter of defining the parameters that need to be chosen in terms of different things like network capacity and processing memory. It then requires specifying the kind of load balancer needed along with some basic inputs. It's easy.

For an average size customer, we manage the entire range of applications and features on AWS. If it fits your use case, it's very good. 

This is a very efficient solution and I rate it nine out of 10. 

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. 

We use EC2 as a disaster-recovery target and also to host a web server. We've got a demo account that uses AT&T Azure managed services where customers can log into our software. 

I like the fact that you don't need to pay for it when you aren't using it, especially in a disaster recovery scenario. The pricing is transparent, so you know what you're going to pay for it. 

If your EC2 instance doesn't boot up, you're in the dark about what's happening. It would be amazing if you could get a view of the console to see the status. There's something called the AWS Console, which is a web portal. I would like to see a virtual screen of an instance that hasn't started properly, so I can see where it crashed. 

I have used EC2 Auto-Scaling for eight years.

EC2 is stable.

EC2 is scalable.

It has gotten much easier to launch an EC2 instance over the years. It's straightforward. We can sign up for EC2 and other web services in a few minutes. Maintenance is something that only comes into play during a disaster recovery scenario. 

I rate Amazon EC2 Auto-Scaling nine out of 10. I recommend setting up billing alarms and paying attention to them. With a cloud platform, it's possible to get a surprise bill if you do something that is running up charges when you aren't aware. 

We use this solution to scale up the number of VM's that are running during times of heavy traffic or high workload. It covers 5,000 servers over 10 different environments for us.

We appreciate that this solution allows us to run all of our severs through it, meaning that our workloads are mainly on the EC2 instance only.

We would like to see improvement in the UI for this solution, so that it is more user-friendly.

We have been using this solution for around six years.

We have found this to be a stable solution during our time using it.

The scalability of this solution is good; we increase our usage gradually and consistently, without any issues.

The setup of this solution is very straightforward. It took us two months to deploy it fully, and migrate our workloads to the cloud from being on premises.

The licences for this solution are based on the number of instances. This determines the EC2 type that is used and this is then priced accordingly.

We would rate this solution a 10 out of 10.