Amazon Elastic Compute Cloud (EC2) vs. AWS CloudFormation

I think nowadays, Amazon EC2 is best-suited for most app development and deployment use cases, especially if your resource requirements are not fixed over a long period of time. The flexibility provided by the on-demand pricing and rescaling option makes Amazon EC2 a great service, especially if your tech stack already runs on AWS. On the other hand, I think Amazon EC2 is not the best option if your tech infrastructure runs on another public cloud.

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

• A great variety of choices in Amazon Machine Image (AMI) types. Users can select a more basic type to run generic workloads, but also have the choice to pick an AMI pre-installed with specific services in the AWS Marketplace.
• The range of instance types can support the usage from a student's exploration (inexpensive general-purpose nano instances) to an enterprise's most intense workloads (memory or storage-optimized instances with terabytes of memory and ultra-fast network connection).
• The pricing options, from regular instances, reserved instances to spot instances allow users to get the job done and make smart choices about how much they want to pay and when they want to pay.

Incentivized

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• This service is a bit difficult to consume. New users need a big learning curve to use this service effectively.
• UI for EC2 service is a little complex and at many places, it misses detailed explanation.
• Sometimes it takes too long to create images of EC2 instances. This keeps your EC2 up for that extra time. When instances are heavy, it penalizes a lot of money.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

Amazon Elastic Compute Cloud (EC2) allows various ways of gaining incidents, such as slow growth, money, and the reserved ones, mostly depend entirely on the necessity, because it makes highly intelligent choices possible at these times, which enable considerable cost savings whilst addressing the situation as best I like.

Incentivized

AWS's support is good overall. Not outstanding, but better than average. We have had very little reason to engage with AWS support but in our limited experience, the staff has been knowledgeable, timely and helpful. The only negative is actually initiating a service request can be a bit of a pain.

Incentivized

Azure VM and Google Compute Engine are alternatives to EC2. AWS EC2 is most matures and advanced of the 3. All these provide easy-to-deploy and automatically configured third-party applications, including single virtual machine or multiple virtual machine solutions.

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

• AWS has had a very positive return on investment for every client we have that uses it. They are saving money in the long run.
• AWS includes the underlying operating system licenses with their EC2 instances so no longer do we have to navigate through Microsoft licensing headache.
• EC2 allows us to easily create a golden image of servers and store them as AMIs. This makes spinning up new servers that need a particular set of software in the future extremely easy and cost-effective.

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized