Amazon EC2 Auto Scaling Reviews

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.

Amazon EC2 Auto Scaling helps maintain application availability and allows you to add or remove EC2 instances.

More than one instance can run at one time. You can start and stop instances at any time.

It can run with any application. Linux, as an example, can be installed with it.

Once the EC2 has been created, you can easily log into it.

The Amazon EC2 Auto Scaling features are simple to use.

The performance is excellent. It's very easy to use and manage.

We have no issues with the integration of Amazon EC2 Auto Scaling.

The user data can be initialized during the startup, which is an excellent feature.

The AMI (Amazon Machine Image) is a helpful feature for the installation process.

I would like to see a feature included that has the capability to clone when an instance is being terminated.

We have a few instances with the internal firewall. If for example, I am going to run Linux, and the firewall is open, sometimes it becomes difficult to debug the issue. Also, when you connect from another device, and if the internal IP address table is not deleted, the firewall will be enabled there. 

There is no clear understanding of where the issue is. If you connect externally, you have to install SFTP.

I would like debugging capabilities included.

I have been using Amazon EC2 Auto Scaling for more than two years.

Amazon EC2 Auto Scaling is a stable solution.

This solution is used by 1,000 people in our organization.

Technical support is good.

Previously, I had not used another solution. I started with AWS.

The installation was fine. We were able to install it with the assistance of AMI.

The installation took less than 10 minutes, but it depends on what you want to install.

This solution is managed by a team of ten administrators.

Licensing fees are paid on a yearly basis.

It is my opinion that serverless, such as Lambda, are preferred over EC2 instances.

I would recommend this solution to others.

I would rate Amazon EC2 Auto Scaling a nine out of 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 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.

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 Amazon EC2 Auto Scaling for production nodes to manage varying loads during peak business hours. It provides the flexibility of auto-scaling infrastructure when there is high traffic.

The product’s most valuable feature is the seamless resizing of web connection.

Amazon EC2 Auto Scaling’s filtering features need improvement. The support to manage the processes could be better. Whenever the product stops working, we have to change the settings and require to find the root cause of the issues. These instance logs should be managed by AWS itself.

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

The product is stable.

We have 1000 Amazon EC2 Auto Scaling users. The platform’s scalability features are flexible. We have recently added a few more nodes, and it was easy to change those configurations. It saves costs and time for us.

My recent experience with technical support is pleasant. They are thorough and quick to contact and coordinate with different teams to resolve the root cause.

We use OpenStack, InfraCloud, and other cloud vendors.

The initial setup process is straightforward. AWS has a user-friendly UI; we also have information and guidance available on their platform. The initial migration process from on-premises to on-cloud takes time.

The deployment process requires having specific knowledge about the application, including its limitations, dependency analysis, and a backup plan. It is preferable to run it in a lower environment and then do actual deployment. If you have a proper plan, it is easy.

The implementation can be in-house. But depending on the team size and management’s decision, we take help from third-party vendors.

We can reduce our infrastructure cost drastically using the product. We have received a good ROI.

The product is expensive. There are no licensing fees, but we have to pay for resources.

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

I advise others to plan carefully. The major challenge is to understand performance and load requirements. You can decide the minimum capacity to be optimized and not over-provision it. Additionally, you can run it in a lower environment before going into production. You can figure out the parameters using CloudOps metrics.

We use EC2 to host applications.

The most useful feature is elasticity. You can scale up or down based on traffic.

The primary area for improvement is the pricing model. 

We have been using EC2 for around 36 months.

I rate EC2 nine out of 10 for stability.

I rate EC2 eight out of 10 for scalability. 

I rate AWS support nine out of 10. 

Positive

I rate EC2 eight out of 10 for ease of setup. The deployment takes four to six hours. Once the application is bundled, it is transported to Site Reliability Engineering, which hosts it. The deployment team consists of four or five people.

We've saved money on resources and infrastructure. The ROI can't be easily defined because it is a cloud service.

I rate EC2 seven out of 10 for affordability. 

I rate AWS EC2 nine out of 10. I recommend it for base production systems.