Amazon EC2 Reviews

It has helped to reduce costs with infrastructure.

Scalability, reliability and easy to use settings. These features are essential for our company.

The services our company offers to our users require high scalability. We need to scale our infrastructure horizontally to meet our users' demands and Amazon can offer this type of elasticity with total reliability.

An advantage of Amazon is that it offers a wide range of infrastructure services with an easy way to configure them.

Price and availability.

I think Amazon could offer lower costs for customers who have a high use demand, as in our case. Nowadays, the cost for little use is attractive, but when your company needs more computing power, costs can be very high.

I believe that a significant improvement to contribute to cost reduction would be a wizard that allows the migration of a certain infrastructure configuration for another solution, such as switching EC2 + RDS instances with a LightSail or Elastic Beanstalk.

Regarding availability, a noticeable improvement would be the possibility of more load balancing configurations and the deployment of more datacenters, mainly in Latin America.

We did not encounter any issues with stability yet.

We did not encounter any issues with scalability yet. One of the greatest advantages of Amazon AWS is the ability to grow on demand.

The technical support is very nice and fast, even for unpaid support.

We've used Google Cloud Platform. We switched because Amazon AWS offers more services and a lot more settings.

Initial setup is always a little bit complex, because we use many services, such as database instances, DNS zones, load balancing setup between multi-zones and so on.

Price is attractive, but at a large scale not so cheap, especially if you use many services. Regarding licensing, we don't have any issue with it.

We were using Google Cloud Platform before using Amazon AWS. We've also analyzed DigitalOcean and a Brazilian datacenter named Locaweb.

You have to consider some factors, like scalability of the services offered by your company. If you need to be online 24/7, then you need a powerful and reliable infrastructure.

Our company, Drivver, uses a wide range of services offered by Amazon AWS, from computational instances to artificial intelligence services, so we need a cohesive and concentrated infrastructure in a single IaaS provider.

As our infrastructure work is outsourced, it's not easy provisioning servers. Even virtual servers take time. Using serverless architectures means no need to involve the infrastructure team.

The serverless architecture solutions are most valuable, and the ability to start with little cost, and then expand as needed.

I think the whole AWS stack is very disconnected from each other. in the .NET space, everything just works nicely together. In the AWS stack, there is a lot of head scratching. Demos appeared easy, however, once you sit down and build a solution its gets very tricky quickly, and as it's a new technology stack, it's much harder to find best practices for common problems.

In terms of EC2 instances, we did notice a handful of times servers were terminated by AWS due to "health checks." Besides that, I think there were one or two major outages that affected a number of AWS systems for a few hours.

No, the serverless stack is actually extremely impressive with how well it scales.

My experience with technical support from AWS has not been good. It all depends on who is assigned as your solutions architect. In terms of finding ways other developers solved issues or best practices in Google searches, as it's a relatively new technology stack, typically I find many people asking same questions and not many answers.

Prior to the AWS stack, we were mostly a .NET stack. Our company partnered with AWS, and looking at their offerings, seemed just using their EC2 offering would be a waste. Having said that, I think using the Azure platform may have provided a better end-to-end solution.

Starting up an EC2 instance is easy, starting an API gateway is also easy, so is setting up a lambda function and a dynamo store. The problem is, what you have just done, from looking at AWS presentations and tutorials, is a bad way of doing things in AWS. You pick up quickly that ideally everything should be scripted using cloud formations, or beanstalk, or serverless, or swagger, etc., and here is where the complexity lies. To do anything properly for an enterprise company, currently its very difficult. What tools do you use? Will they still be around in six months?

Pricing appears to be cheap, however, it is extremely difficult in calculating what something will cost. Someone accidentally starting a EC2 server could end up costing you notable dollars. Also once you start using services, let's say serverless architecture, you may quickly find you need to build dirty solutions just to keep the price down, or even go back to server based solutions due to costings.

For some services like API Gateway, we did look at some other options, however, the serverless architecture concept was new and not available as a stack with any other company at such a competitive price. Now Microsoft has also joined the concept, and while I have not used the Microsoft offering, based on my other experience with the .net platform, i think it may be a better platform.

For small startups it makes perfect sense. For large organizations with R&D team/budget, it may make sense. For medium-size companies, where they just need solutions built quickly, I am not convinced about AWS at the moment. Looks promising, but it's a very new platform, with issues that come with a new platform.

I believe that cloud solutions are better than physical servers. 

I am concerned about the tool's data security. 

I am using the product for an year. 

I would rate the tool's stability a ten out of ten. 

The solution is fully scalable. We have five to six clients who use the tool. 

The tool's setup is a bit complicated. You need to have some amount of technical knowledge to install it. The deployment gets completed within three months. We need to first connect to the instance and generate a token. Post that we need to connect to the additional server and then to the cloud. 

I would rate the tool a nine out of ten.