Amazon EC2 Reviews

Use cases for Amazon EC2 that I work with involve many projects such as making virtual machines, and as per the requirement of our clients, I set all the storages and virtual machine types, including Windows Server. I have faced different use cases in my work.

I work with Amazon EC2 as a service provider.

Clients have shared their experiences with Amazon EC2 regarding on-demand pricing and scalability, noting that elasticity is a key feature along with high availability, custom AMIs, and the best and wide instance selections. They appreciate the global infrastructure, secure isolation, and integration with AWS services for backup and recovery, which they find beneficial.

Amazon EC2 has significantly improved our organization's IT operations in the following ways:

1. Scalability:

With EC2, we can easily scale our compute resources up or down based on real-time traffic and workload demands. This has helped us maintain performance during peak hours without overpaying during low-usage times.

2. Cost Efficiency:

By using features like Reserved Instances and Auto Scaling, we've optimized costs. We only pay for what we use, and we can forecast expenses better than with traditional servers.

3. Reliability & Availability:

EC2 instances, combined with Elastic Load Balancing and Multi-AZ deployments, have improved our application's uptime and fault tolerance.

4. Speed & Flexibility:

Launching new instances for development, testing, or production use is much faster than provisioning physical servers. It has drastically reduced our time to market for new features and services.

5. Security & Compliance:

With AWS Identity and Access Management (IAM), security groups, and VPC controls, we've improved our security posture while meeting compliance standards.

If EC2 hadn’t improved your organization, you might respond like this:

EC2 didn’t significantly improve our organization due to the following reasons:

1. Limited Cloud Readiness:

Our legacy applications were not cloud-optimized, making migration to EC2 complex and costly without re-architecting.

2. Skill Gaps:

Our team lacked experience in managing cloud infrastructure, which led to configuration issues and underutilization of EC2's features.

3. Cost Management Challenges:

Initially, without proper monitoring and cost control tools, we faced unexpected bills due to overprovisioned instances and lack of auto-scaling.

Amazon EC2 features that I have found the most valuable and useful include elasticity and scalability, a variety of instance types, pay-as-you-go pricing, security, isolation, AMIs, integration with other services, Spot Instances, and high availability of reliability, user data, and EC2 metadata. These include Amazon EC2 images, image builder, and auto scaling as instance types, pricing models, and security with VPC, IAM roles, and security groups.

The most beneficial features of Amazon EC2 for cloud operations are EC2 Auto Scaling with Elastic Load Balancing, which allows scale up and scale down, maintains high availability, and optimizes costs. Auto Scaling provides fault tolerance, performance optimization, and cost efficiency. A real-world benefit is that an instance automatically handles the load. When traffic drops, it reduces the number of instances.

Other highly beneficial Amazon EC2 features include Spot Instances, multiple instance types, custom AMIs, VPC security groups, strong network and access security, and Elastic IPs, which are the static IPs for dynamic instances.

The pricing of Amazon EC2 can be expensive, so I would rate the pricing seven out of ten, where one is very cheap and ten is very expensive.

I have been working with Amazon EC2 for two years.

All instances provided by Amazon EC2 are in 24-hour running mode. They experience some problems. This is critical for enterprise-grade workloads, which are built on high-reliability infrastructure such as Amazon Global Data Centers. Each availability zone is isolated with independent power, cooling, and networking systems, ensuring fault tolerance and offering auto-recovery features.

Auto scaling and load balancing are available, making it reliable with strong options. Amazon EC2 supports Amazon EBS, which offers 99.99% availability, along with snapshots, backups, and disaster recovery. Global reach and redundancy of multi-Amazon developments ensure high availability failover.

Scalability in Amazon EC2 includes two types: vertical scaling and horizontal scaling. Scalability impacts how it handles sudden traffic spikes. On a sale day, if your website gets 10x more traffic, Auto Scaling adds Amazon EC2 instances and handles the load smoothly, reduces costs, and improves reliability and uptime.

Based on my experience with scalability in Amazon EC2, I would rate it nine out of ten.

Amazon EC2 has technical support, which is a great option, and they provide very fast answers to inquiries. I would rate it eight out of ten.

Positive

Yes, we used a different solution before switching to Amazon EC2:

Previously Used Solution: On-premises physical servers / local data center.

Why We Switched to EC2:

1. Scalability Limitations:

Our on-premises infrastructure could not scale quickly during high-demand periods. Adding new servers took days or weeks.

2. High Maintenance Costs:

We had to maintain hardware, handle power and cooling, and manage physical security. EC2 eliminated those overheads.

3. Lack of Flexibility:

Physical servers lacked the flexibility to quickly spin up test environments or deploy applications in multiple regions.

4. Business Continuity Risks:

We had limited disaster recovery and backup capabilities. EC2’s multi-AZ and snapshot features improved our resilience.

5. Global Access & Agility:

With EC2, our remote teams and customers across different regions now experience better performance and uptime.

If you have seen positive ROI:

Our ROI from Amazon EC2 has been strong, both in financial and operational terms.

1. Cost Savings:

We've reduced infrastructure costs by eliminating physical server maintenance, power, cooling, and real estate.

 Reserved and Spot Instances have lowered our compute costs by up to 60–70% for steady and flexible workloads.

2. Operational Efficiency:

 Our team spends less time managing servers and more time on innovation and development.

 EC2’s scalability helped us avoid downtime during peak loads — preserving both revenue and customer satisfaction.

3. Faster Time to Market:

New environments can be launched in minutes instead of weeks — speeding up deployment and reducing opportunity cost.

While we don’t disclose specific ROI numbers, the return in terms of agility, uptime, and lower TCO (Total Cost of Ownership) has been substantial.

We implemented EC2 through our in-house team.

> Our internal IT/cloud engineers handled the setup, configuration, and deployment of EC2 instances. This gave us greater control, allowed for tailored architecture decisions, and helped our team build hands-on AWS expertise.

 We leveraged AWS documentation, training resources, and online communities to support the implementation process. It also helped us upskill the team for long-term cloud management.

If you used a vendor/consultant:

We implemented EC2 with the help of a vendor team.

Their AWS-certified professionals brought deep knowledge of EC2 and overall cloud architecture. They guided us through:

 Instance sizing

 Network and security setup (VPCs, IAM, security groups)

 Cost optimization strategies

 High availability and backup planning

If you have seen positive ROI:

Our ROI from Amazon EC2 has been strong, both in financial and operational terms.

1. Cost Savings:

We've reduced infrastructure costs by eliminating physical server maintenance, power, cooling, and real estate.

Reserved and Spot Instances have lowered our compute costs by up to 60–70% for steady and flexible workloads.

2. Operational Efficiency:

Our team spends less time managing servers and more time on innovation and development.

EC2’s scalability helped us avoid downtime during peak loads — preserving both revenue and customer satisfaction.

3. Faster Time to Market:

New environments can be launched in minutes instead of weeks — speeding up deployment and reducing opportunity cost.

While we don’t disclose specific ROI numbers, the return in terms of agility, uptime, and lower TCO (Total Cost of Ownership) has been substantial.

Advice on Setup Cost, Pricing, and Licensing for EC2:

1. Start Small & Use Free Tier if Possible

For new users or small applications, the AWS Free Tier offers limited EC2 usage free for 12 months. It's a great way to test without upfront investment.

Always right-size your instances — don’t start with more CPU or RAM than you need.

2. Understand EC2 Pricing Models

On-Demand Instances : Best for short-term or unpredictable workloads. No upfront cost, but more expensive per hour.

Reserved Instances: Ideal for steady workloads. You commit for 1 or 3 years and get up to 72% discount.

Spot Instances: Best for flexible workloads that can tolerate interruptions. Extremely cost-effective — up to 90% cheaper.

3. Use Auto Scaling & Load Balancing

 Set up Auto Scaling Groups to automatically increase/decrease instances based on demand.

* This ensures performance while controlling cost.

4. Monitor and Optimize Regularly

 Use AWS Cost Explorer , CloudWatch, and **Trusted Advisor** to monitor usage and optimize cost.

Set up budgets and alerts to avoid unexpected charges.

5. License Considerations

AWS offers License Included EC2 instances for Windows Server and some enterprise software — no separate license purchase needed.

 If you already have licenses (e.g., Windows, SQL Server), you can use  Bring Your Own License (BYOL) in eligible cases.

6. Don’t Forget Hidden Costs

Storage (EBS), bandwidth (data transfer out), and additional services (like Elastic IP, snapshots, etc.) can add up.

Review all charges regularly in the Billing Console.

Final Tip:

Plan first. Deploy later. Create a small proof-of-concept, analyze costs, and then scale. EC2 can be extremely cost-effective if used wisely — but also expensive if misconfigured.

Yes, we evaluated other options before choosing Amazon EC2:

Before selecting EC2, we explored several alternatives, including:

1. Microsoft Azure (Virtual Machines):

Azure was a strong contender due to its integration with Microsoft tools like Active Directory and Office 365. However, we found EC2 more flexible in terms of instance types, pricing models, and global infrastructure.

2. Google Cloud Platform (Compute Engine):

GCP offered solid performance and competitive pricing, but at the time, AWS had a more mature ecosystem, better documentation, and wider third-party support.

3. Local Hosting Providers / VPS Solutions:

We also considered local virtual private server (VPS) providers due to lower latency and localized support. However, they lacked the scalability, automation, and advanced features offered by AWS EC2.
Why We Chose EC2 Over Others:

Better global infrastructure and availability zones.

More mature service ecosystem (with S3, RDS, IAM, etc.).

Flexible pricing options like On-Demand, Reserved, and Spot Instances.

Strong community support** and extensive documentation.

Integrated security and compliance features.

Amazon EC2 has all features that provide the best response. You only pay for needed compute resources, which is optimal. An instance provided by AWS on a based processor delivers up to 40% better performance over the AMD instance and has lower energy consumption, making it eco-friendly. A major improvement in cost, speed, and energy is something we can upgrade, and that makes it more beneficial. My overall rating for Amazon EC2 is 9 out of 10.

We use Amazon EC2 for our databases as well as CRM DNS to host our applications. For 3D architecture, we use the EC2 constraints.

The most valuable feature for Amazon EC2 is its integration with other services. System Manager is available from AWS, which handles patching as well as server minimums. That is a significant advantage for us.

Amazon EC2 has provided automated patching through Patch Manager and System Manager, which is under System Manager.

During the initial setup, we downloaded a certificate because we could not find proper documentation for it. There should be clear direction based on whether you are using Linux or Windows. There was not proper documentation on how to install the patch managers and automate patching with System Managers.

The solution that has been provided is good, but AWS needs to provide better documentation. We work better now that we understand how to implement it.

I have been using Amazon EC2 for two years.

For stability, I would rate it an eight; it is somewhat more reliable compared to Azure.

On a scale from one to ten, I would rate the scalability for Amazon EC2 a seven.

The support from AWS could be better, but that is not directly related to Amazon EC2. It is more on the technical side.

I had some issues that I had to contact them about. However, we did not receive a clear answer to what people were expecting.

On a scale from one to ten, I would rate the AWS support team a seven.

The initial setup for Amazon EC2 is straightforward.

If it is a simple setup with a single user, it can take more than two days. If it is for a bigger project where you need to take care of data security as well as client requirements, it should take around two to three weeks for the initial requirement analysis. After that, it should take more than a week to set up Amazon EC2 to meet the client's requirements.

I have seen a return on investment for my client.

The licensing fees for Amazon EC2 are affordable, especially for lower tiers where there are fewer requirements or where the load is very low for product development. The pricing is very much affordable.

For billing, I am not certain, as we do not handle the billing. However, during my training and initial hands-on experience while I was learning, it was very affordable.

My advice for Amazon EC2 is to follow the documentation provided by AWS. That would help considerably. I would rate this review an overall eight.

I used Amazon EC2 for application management and application hosting. Apart from Amazon EC2, I have experience with RDS and S3. I have also used different components of AWS for routing and file management.

When starting my development career, I noticed there were multiple hosting platforms that give you ready-made solutions where you just mention your requirements. However, Amazon EC2 offers flexibility. You can do anything with Amazon EC2 as you have a bare system in your hands. You can set it up, manage your files, change the configuration, and more. That is the best part of Amazon EC2 compared to other hosts.

Initially, I was not sure how things were working. After I became familiar with it, I didn't feel any issues with Amazon EC2. However, one concern remains. I have heard from multiple people that if you have an Amazon EC2 instance running and you stop it, the billing continues unless you terminate the Amazon EC2 instance. This is an area where users should be prompted. I am not sure whether that information is currently available, but users might think billing stops when they stop their instance.

I have been using the Amazon EC2 tools during my development phase.

Working with a load balancer, I haven't faced any stability issues so far.

I am not directly involved in this part, as I am using Amazon EC2 as a tool currently.

I would definitely recommend Amazon EC2, and I have already recommended it to several friends who are in development and wanted to set up their applications for the Internet. They are happy with this service.

Previously, I had access to the AWS console while managing my own products. Now within the organization, we have limited access where we can get IP addresses, IP pools, and check instance stats. I am a user of these features rather than managing them.

On a scale of 1-10, I rate Amazon EC2 a 9 out of 10.

We use Akamai for our CDN and our WAF into our AWS accounts. The Akamai part of it is handled by a couple of engineers in my department, but I don't really have much interaction with them. As an end user, I personally use it very rarely. I am now more involved in the databases, using Amazon Aurora and deploying EC2s with Couchbase on them. We use Couchbase on Amazon EC2 and deploy the database onto it.

The most useful function of Amazon EC2 for us is compute. We find it easy to deploy our database onto it. It is easy to integrate with other AWS solutions. There are no complexities or issues with that integration. We rely on their generic encryptions, so nothing fancy regarding Amazon EC2 security features. The main benefits Amazon EC2 provides for me as an end user are cost savings, as they are more OpEx costs rather than CapEx for us. We use Amazon EC2 as a building block, so I don't see any need for improvement, as it seems to do the job fine.

The price for Amazon EC2 could be lower; it's not cheap, so when we want something cheaper, we do go serverless if we can. From my side, a point for improvement is definitely the pricing. It could be cheaper.

I have been working with Amazon EC2 for approximately five to six or seven years.

I would rate the stability of Amazon EC2 a 10.

Amazon EC2 is very scalable.

I would rate technical support from Amazon a 10, as we have on-prem AWS experts. This is a 10 because we have AWS people on-site here.

We have moved on from Pulse, now known as Ivanti Virtual Traffic Manager, and we don't have any on-prem kit anymore, so we have moved entirely to AWS.

The initial setup for Amazon EC2 is very simple.

I'm not sure about a competitor for Amazon EC2. Google's Compute could be a competitor for Amazon EC2. Our department started with AWS, while other departments use Google Compute, so we tend to use AWS.

My main use case for Amazon EC2 is for developing and testing.

I can provide a specific example of how I use Amazon EC2 for testing, which includes both performance testing and automation, as well as finding bugs in the software.

We are using Amazon EC2 for all of the infrastructure services, including domain controllers, file transfer, and any tasks related to developing the software.

The best features Amazon EC2 offers include the ability to increase resources anytime, add storage anytime, change the instance type, and deploy new instances quickly if using an AMI.

I find myself using the ability to increase resources anytime the most, as it has made the biggest difference for my team.

Amazon EC2 has positively impacted my organization because it is easy to deploy. Whenever we have on-premises infrastructure and need to order servers, it takes a long time for delivery. However, with the cloud, deployment is easy, and within a minute, we can deploy the server and give it to the developers so they can work on it right away after deployment.

I think improvements can be made to Amazon EC2 by increasing the memory, offering more instance types, and including GPUs as mentioned in the keynote. In the future, I think you could explore quantum processors, which would be a good idea.

I have been using Amazon EC2 for more than five years.

I would say I have saved more than a week with Amazon EC2 compared to my previous on-premises setup. Now deployment takes within one hour with AWS, whereas it previously took much longer.

My advice for others looking into using Amazon EC2 is to look at the instance type they need and select the appropriate instance type accordingly. I give this product a rating of 9.

I have several years of experience with Amazon EC2. I work with Amazon EC2 for compute and S3 buckets.

From the features perspective, I find the most beneficial features of Amazon EC2 for server management to be very impactful.

From the security point of view, I find the security features in Amazon EC2 to be effective in safeguarding my data.

I can elaborate on how the scalability has impacted my operations using Amazon EC2.

I have had AI driven projects and initiatives that were supported by the Amazon EC2 solution. From the performance point of view, I find Amazon EC2 to be stable.

There are some specific features, such as ML features and AI features, that I would to see included in the next releases of Amazon EC2. Additionally, there is functionality available in Databricks and other competitors that I would to see included in Amazon EC2 as well.

I don't have much AWS experience at present, but I usually work more with AWS, and less with GCP and Azure.

I can share my experience with the initial setup of Amazon EC2 and the AWS environment. It was smooth, straightforward, and not challenging at all.

The pricing is reasonable. I can discuss the cost-effectiveness and the return on investment from the Amazon EC2 product.

I have been working with AWS for a very long period of time. I would recommend Amazon EC2 overall and share my advice with others who are considering it. On a scale of one to ten, I rate Amazon EC2 a ten out of ten.

Positive

Positive

In most cases, I have customers coming to me inquiring about cloud computing, specifically how they can be assisted and utilize AWS. They want to understand how they can position themselves to use AWS EC2 instances efficiently. Some of the concerns that clients have looked into include security and scalability, and often customization as well.

Within the EC2 instance, there are a number of features depending on what the client is looking for as EC2 instances on AWS allow users to run virtual servers based on the CPU, memory, storage, and networking capacity. This is based on each client's needs, which are always different. The flexibility of it is crucial, and one great aspect is the customization. This allows users to choose operating systems like Linux or Windows or perform software checks based on their application requirements. It's always great.

There is not much to be improved or enhanced. One of the things that need to be looked into is the complex pricing, which is rather intense. Sometimes, clients don't understand the structures. These are some of the complex aspects that have happened before within the EC2 instances, like complex pricing based on various instance types, storage options, data transfer costs, and challenging cost estimation and proper monitoring since not every client has a workflow that is easily managed.

I have used the solution for over five years.

The system is very stable. It's easy to increase resources. They are boosted in different AWS regions. 

However, availability zones might suffer from high latency, depending on which availability zone the client has chosen. It depends on whether the place you've chosen is mature enough to bring a low level of latency. That's what I normally look into.

Scalability depends on whether the client wants to scale up or scale down. It decreases resources based on demand. The great aspect of scalability is the flexibility to allow business success to optimize resource solutions and cost efficiency. 

Another crucial aspect of scalability is auto-scaling. When you have the opportunity to auto-scale, it can't always be available for everything. If you have chosen to integrate with auto-scaling, it's marvellous and doesn't require additional effort. Auto-scaling gives you the edge by using the capacity you have efficiently, scaling up or down as needed. 

These flexibilities within the EC2 feature instances of AWS play a crucial role in helping me utilize AWS EC2 Intelligent efficiently.

From my organization, we give the best support we can. The support provided is rated ten out of ten, as we have organizations that write testimonial letters about the support they have received.

Positive

The difficulty of the initial setup is mostly based on whether the individual understands AWS. You cannot set it up if you are not a technical person. You need to be technical to understand EC2 instances. 

The easy part is creating an account within AWS. However, setting up the other components requires understanding to avoid complexity in pricing or other misunderstandings. 

There is a workflow available for people to understand. It is based on individual preferences. From my side, I'm going to give the setup an eight out of ten. It's understandable to set it up, patch it, and ensure it's available.

I'm not that technical and I have a technical team that deploys it. I just make myself available in terms of deployment. In terms of the technicality of it, I don't know the steps.

I'm going to mention again that there is quite a bit of complexity within the pricing of EC2 instances. I'm just going to give it six out of ten since there are various standards, upfront and committed pricing, storage options, and data transfer. It's always different.

A recommendation would be based on whether the individual understands AWS. You cannot set it up if you are not a technical person. You need to be technical to understand EC2 instances. AI is going to play a role in each cloud opportunity, simplifying connections. Amazon has its own general AI. It's a win-win situation for them as they know what they are doing. It can also impact simplifying how other instances or opportunities within the EC2 environment can be managed. 

The overall product rating is nine out of ten.

My primary use case involves deploying multiple applications, such as web applications, database applications, and reporting platforms on EC2 instances. I use EC2 for creating and managing servers, integrating with Docker and Kubernetes for containerization, and automating tasks through Terraform scripts. My customers typically require different configurations, like Linux servers or specific database endpoints.

One of the most valuable features of EC2 is its accessibility; I can easily access it through various tools like GIT and use it on mobile devices. EC2 allows me to create servers with specific configurations, and its scalability supports different application workloads. It also provides features like auto-healing, load balancing, and integration with Docker for creating containers managed by Kubernetes.

An area needing improvement is the time limitations when accessing EC2 instances. When accessing the server, sometimes PeerSpot can fail, making it difficult to access multiple servers simultaneously. Increasing the time window for log checks and application access would be beneficial.

I have been working with Amazon EC2 for four and a half years.

EC2 exhibits high stability. I have not experienced any crashes with the servers or containers. The solution runs smoothly without any noted stability issues.

The scalability of EC2 is highly commendable, especially with its horizontal scaling features. Autoscaling efficiently handles increases in application traffic by creating additional instances as needed.

I have not interacted with EC2's technical support extensively, except for billing inquiries earlier in my career. Therefore, I can't provide a detailed assessment of their customer service.

Neutral

In terms of hybrid cloud solutions, I have also used Google Cloud Platform alongside EC2, gaining certification for specific projects. However, I prefer using AWS due to its easier configurations and accessibility.

The initial setup of EC2 is straightforward and user-friendly, earning a rating of nine and a half out of ten. Setting up instances and launching applications is seamless with existing scripts.

Typically, the implementation of EC2 requires a small team. In DevOps settings, the pipeline requires monitoring with around two people, while establishing new pipelines involves three to four members, depending on the traffic and complexity of the projects.

The pricing of EC2 can vary depending on workloads. It can be expensive for high workloads but more cost-effective for smaller applications. AWS provides various services at competitive pricing, making AWS a favorable choice for startups and smaller projects.

I have worked with Google Cloud Platform as an alternative solution in the past.

Amazon EC2 is a robust and versatile solution ideal for deploying various applications. It provides excellent services compared to competitors. Despite being costly for high workloads, it offers unmatched features and flexibility. 

My overall rating for Amazon EC2 is ten out of ten.