What is our primary use case?
I primarily use Amazon AWS and EC2 services. The primary use case is to spawn servers quickly with a particular hardware memory, CPU, and storage footprint. It gives me a hardware service quickly, I can get a virtual machine with Linux installed with a particular storage configuration. I can also configure the security and bring it up.
Practically, it gives me a mini data center in one or two minutes.
We need to bring a large number of servers to do our jobs. We do a lot of crawling jobs hosted in AWS. We have templates available to us to bring a pool of servers up and running, hardware as a service.
In our use case, it's not the number of users using the solution, it's more the number of processes that respond. Based on the compressions and the jobs we do or sometimes we crawl, so the scaling is more in terms of the amount of data acquisition we do.
How has it helped my organization?
The ability to bring up servers and then do the computation and deposit means we don't have to maintain a data center. Everything is virtual and the security is also taken care of. It helps us to achieve compliance. Being a small startup with the security features that AWS provides helps us with compliance.
The encryption, storage, physical security, and data security features at the protocol and storage level, helps us as an organization to achieve greater compliance and keep our business running in a secure fashion.
What is most valuable?
The features I find valuable are EC2, the admin control, and the ability to add the elastic IPs and then attach storage; all of those features are valuable. Also, the Admin Control, Cost Explorer, and the billing features are valuable. That gives me the ability to understand the costs. Amazon AWS has some savings plans.
In cloud computing, people think the cloud is cheap, but you need to know how to use it and configure the right plans.
AWS Cost Explorer and the billing features are also valuable.
S3 buckets and fast storage are also very nice features.
What needs improvement?
In terms of improvement, they could build some client-side desktop tools that provide easier connectivity to Amazon.
For how long have I used the solution?
I have been using Amazon AWS for 3 years.
What do I think about the stability of the solution?
In terms of availability and stability, they have not been an issue so far. I've used it in all previous organizations for very large-scale deployments and they're working fine.
We are not seeing any outages because of Amazon, except if we are using spot instances, they can go down at any moment. We will only use these when we can afford server downtime, so not for production. They sometimes can go down for an hour and so on, but other than that the EC2 instances are fairly stable and great, we have not had an issue so far.
What do I think about the scalability of the solution?
Scaling is not a problem because they themselves give you Amazon auto-scaling features. Very few users know how to use it properly. Our VM and images should be properly packaged and then you have to configure it. The load boxes have to be configured, you need to do some configuration, then you can basically vertically scale by choosing a server with a larger memory footprint, or you can go for horizontal scaling by adding more configuration into it. It's scaling over the box.
How are customer service and support?
I've never had to use Amazon support services yet. I've not opened any tickets so far, I don't have first-hand experience of going through the support process with Amazon. I have been supported by their enablement teams that work with startups, they are fairly good.
Which solution did I use previously and why did I switch?
I've been using AWS for quite a while, there are some use cases where I have not directly used any other cloud product so far, I mostly stick to Amazon.
How was the initial setup?
The initial setup is more or less straightforward for a developer. For somebody who is not from a pure development background it obviously requires you to understand what a public IP address is. You need to understand what storage is and then how to use it. It's mostly for developers and administrators, not for a non-technical audience; for people who can configure a server and have technical background.
What about the implementation team?
We mostly implement everything on our own, we don't have to bring in a consultant. The only time we brought in a consultant from AWS itself was to take up the offer of a free review of our infrastructure and they will help us to optimize. They advise on which plan based on our use case. Other than that, most of the technical documentation is available and we can operate on our own.
What's my experience with pricing, setup cost, and licensing?
If we already have the script and everything available, the deployment takes no more than half an hour. We already have the templates, but the template development, the scripts, all the tools development will take some time, maybe a month or so depending on the use case. But, once you have them set up, it's basically a matter of 15 minutes to half an hour.
There were no annual or monthly licensing costs as it's completely based on usage. Depending on how many hours of use, the instance we run, and the storage we use, you get a very detailed account of usage in your billing document.
Which other solutions did I evaluate?
I did not go through an evaluation process beforehand, mostly it was chosen by the organizations. I did evaluate other vendors on cost optimization to see whether switching to another vendor would improve cost.
I wanted to optimize the infrastructure to see whether the problem is with the way we use it or if Amazon itself is expensive. I was able to bring down the cost with some of the cleanups and saving plans they offer.
What other advice do I have?
We plan to increase usage as our business expands, we will grow with AWS as it expands.
In terms of the EC2 services, it's an amazing product, in terms of the computational power and the flexibility and then the number of features and services they provide, it's awesome actually.
I would rate it a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.