Amazon EC2 Auto Scaling Reviews

We have several instances and applications that we run using WordPress. For that, I needed an easy, secure, and faster solution with different options to back up the website and data. Amazon EC2 offers options to back up data using the S3 version control system, which worked really well for us. Moreover, it's cost-effective.

Having a load balancer in between is very helpful when you have huge traffic. It has been beneficial for handling around 80,000 to 200,000 visitors a month on our blog.

There is room for improvement in the scalability.

I have been working with this solution for a couple of months. So, it's been three to four months.

I would rate the stability a nine out of ten. 

I would rate the scalability an eight out of ten.

The initial setup is definitely more complex than any of the readily available tools. But, it's okay. It's well-documented, so it was not a big deal for me.

The deployment took me around a week, and it's been running for three months in a row. But yeah, we are still testing.

It's not expensive, nor too cheap; it's okay. We can compare it to the pricing of other cloud service providers.

Right now, EC2 is in the testing phase, and we are still using Cloudera and DigitalOcean. However, I'm looking for solutions that could be more helpful in the long run. Additionally, I've used Amazon RDS as the database provider because our CMS has become heavy over time. So I had to offload the database into RDS and connect it with EC2.

When using Amazon EC2 Auto Scaling, it's crucial to have a solid understanding of cloud computing and infrastructure management. That's very essential.

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

At CPA, we have a product where we manage several aspects, but essentially, one of them concerns managing campaigns during specific days in the USA, such as holidays or weekends. During these times, we experience a high demand from people using the systems, which necessitates the use of Auto Scaling.

Amazon EC2 Auto Scaling manages peak traffic demands by allowing the creation of rules based on network requirements or specific scheduling needs. This ensures flexibility and efficiency in handling increased traffic on days with high demand, such as holidays.

The configuration capabilities and the flexibility that it provides are most valuable. With the ability to set up rules based on demand, network, or traffic, the service offers a necessary level of adaptability.

Sometimes the configuration is not intuitive. Maybe the documentation could be clearer in certain areas. 

While understanding the tool is straightforward, there could be improvements in how intuitive the setup and the documentation are.

I have been using Amazon EC2 Auto Scaling for nearly six years.

Stability depends on the applications. If there are software-related issues like poor memory management, instances may restart or fail, however, Auto Scaling effectively handles this by dynamically creating new instances as needed. Thus, I consider it highly reliable.

It offers almost perfect scalability, adapting well to various demands, especially during peak periods such as holidays.

During these six years, I have not needed to reach out to technical support.

Positive

Setting up is not complicated once you understand how to manage the tool, and it is primarily an issue of communicating with business stakeholders to understand their needs.

Considering the expenses associated with the instances themselves, I would rate it a six. While instances can be costly depending on their number, the cost aligns with the value provided.

One should pay careful attention to the configuration of policies. Misconfiguration could lead to undesirable costs since resources may not be optimally used.

I'd rate the solution nine 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.

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.

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.

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. 

The tool serves several purposes. It helps to pass instances automatically. We can perform maintenance on instances and application upgrades.

The solution incorporates ease of maintenance and reduction in operational overhead and costs. Patching is also easy. 

The most valuable feature is the tool's ability to integrate with load balancers. 

The launch configuration feature doesn't work properly. It needs to improve the load configuration feature along with launch templates. The tool needs to tag feature as well. 

I have been working with the solution since 2016. 

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

I rate the tool's scalability an eight-point five out of ten. 

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

I rate the product an eight 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.