Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides secure, resizable compute capacity in the cloud. Users can launch instances with a variety of OSs, load them with custom application environments, manage network access permissions, and run images on multiple systems.
$0.01
per IP address with a running instance per hour on a pro rata basis
Amazon Web Services
Score 8.6 out of 10
N/A
Amazon Web Services (AWS) is a subsidiary of Amazon that provides on-demand cloud computing services. With over 165 services offered, AWS services can provide users with a comprehensive suite of infrastructure and computing building blocks and tools.
$0
per month
Pricing
Amazon Elastic Compute Cloud (EC2)
Amazon Web Services
Editions & Modules
Data Transfer
$0.00 - $0.09
per GB
On-Demand
$0.0042 - $6.528
per Hour
EBS-Optimized Instances
$0.005
per IP address with a running instance per hour on a pro rata basis
Carrier IP Addresses
$0.005 - $0.10
T4g Instances
$0.04
per vCPU-Hour Linux, RHEL, & SLES
T2, T3 Instances
$0.05 ($0.096)
per vCPU-Hour Linux, RHEL, & SLES (Windows)
Free Tier
$0
per month
Basic Environment
$100 - $200
per month
Intermediate Environment
$250 - $600
per month
Advanced Environment
$600-$2500
per month
Offerings
Pricing Offerings
Amazon Elastic Compute Cloud (EC2)
Amazon Web Services
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
AWS allows a “save when you commit” option that offers lower prices when you sign up for a 1- or 3- year term that includes an AWS service or category of services.
More Pricing Information
Community Pulse
Amazon Elastic Compute Cloud (EC2)
Amazon Web Services
Features
Amazon Elastic Compute Cloud (EC2)
Amazon Web Services
Infrastructure-as-a-Service (IaaS)
Comparison of Infrastructure-as-a-Service (IaaS) features of Product A and Product B
Suitable for companies that are looking for performance at a competitive price, flexibility to switch instance type even with RI, flexibility to add-on IOPS, option to lower running cost with the regular introduction of new instance type that comes with higher performance but at a lower cost.
We are using RDS for the database services. With RDS, we don't have to manage much, as most of the DBA tasks are automated. For development purposes, we are using Kubernetes pods, which makes it easy to deploy applications and scale up as needed. AWS integration with in-house applications is seamless, making it easy to keep a data-sensitive application on-premises while still utilizing AWS services.
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.
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.
I would gladly rely on AWS for any large-scale application deployment. For prototyping and small-scale applications, a more heavily managed environment on top of the 'bare metal' virtual infrastructure, such as Heroku or Elastic Bean Stalk, is probably a more productive approach in most cases
It's easy and straightforward for a technical person to use it via SSH, but when working in cross-functional teams, using Amazon's web console is difficult for this particular service. Most modern cloud providers provide a more seamless user interface to interact with their cloud machines, and the same should have been the case with EC2.
Amazon Web Services is a great tool when it comes to middle size organizations like us. It provides multiple tools and functionalities in low costs. The best feature we have to pay as we go. No financial burden on company for the unused instances. It also comes with greater level of security such as two level authorization such as multi factor authorization.
AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.
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.
The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to immediately search for their compatible software's and also to guide them in a good direction. Moreover, this product is a good suggestion for every type of company because of its affordability and ease of use.
Azure VM Builder offers good service, but the options are quite limited (Too much inclined to Windows as it is prepared by Microsoft). EC2 image building capabilities are the best in the market, and offer Windows, Linux (CentOS, rh2, debian, ubuntu), along with other distros, which helps customers choose according to their needs.
In my personal experience, AWS is superior to both GCP and Azure in the majority of usable applications. GCP suffers from the near total misunderstanding of how support system is even supposed to work, and while _some_ services are pretty nifty and well-polished, some are mindbogglingly designed black boxes with self-conflicting documentation. Some of it comes from having legacy systems, sure, but AWS somehow manages, even having a rather big lead start. Azure, from my limited experience, is limited to people somehow coerced into its usage by external constraints. That being said, IF you can design and implement something there, it will probably run fine.
With EC2 you pay only when is Running, so you can save up to 75% on Dev environments which are running only on office hours
You have several ways to pay for EC2, with EC2 Reserved Instances you pay with a discount of up to 72% if you make a commitment of using them from 1 or 3 years
With EC2 spot you can use spare AWS EC2 capacity with a discount of up to 90%, your workload must be interrupt tolerant as your EC2 could be reclaim by AWS and the EC2 terminated
Provisioning resources like large database instances is really quick. We can easily scale our instances up or down as per need.
Storing files in S3 instead of onprem NAS drives is much more economical, especially for the files stored in glacier deep archive for compliance purposes.
Backup snapshots of EBS volumes and RDS instances may increase the cost of cloud if not cleaned up properly.