Contrasting AWS Instances at a Glance and fixing Up the right one for you !

It’s cumbersome to choose AWS as the essential provider of our Cloud Services and now when we’re looking into setting up our environment. We’ve got our project to be deployed and all we are left to do is choose an AWS instance that will run our machine image .But, now like many others before us are stumped by the countless choices of EC2 instances out there, leaving behind the wallet constraints and effectiveness of our cloud environment. Most obviously the new AWS users encounter such obstacles that they need to overcome in due time. Along with the varied types of instances , the different AWS EC2 pricing options increase the chances of uncertainty .

For example, purchasing i3EN 3XLarge for its memory and CPU specs is a choice that will leave you with an extra $2k expense in your annual bill when you can gain the same size for a cheaper price by purchasing Z1D 3XLarge instead.

We could definitely collate instances and filter it by our preferences and view the different instances from lowest to highest EC2 prices. Some important points to keep in mind :-

  • One needs to choose from compute-optimized instances, General purpose instances or any other instance type, filter them according to the memory or vCPU specs you have in mind and view your narrowed down the list of instances according to the price from lowest to highest.
  • Try changing the pricing model from AWS Reserved Instances of Windows or Linux to On-Demand pricing.
  • Click on the data points to compare multiple instances.
  • View the prices as hourly, weekly, monthly or annually.

Easy Amazon EC2 Instance Comparison can be broadly analyzed here :-

AWS Instance Types And Comparison

AWS cloud computing options, namely Amazon Elastic Compute Cloud Instances (Amazon EC2) and the Amazon Relational Database Service (Amazon RDS) are the different AWS instance types and a comparison of different use cases for each will be discussed below.

AWS — Amazon RDS vs Amazon EC2 Relational Databases

Amazon EC2 vs Amazon RDS

Amazon EC2 Instances are essentially the same as a computer/server within our organization, except the computer/server is located elsewhere. Rather than buying the hardware, you rent virtual machines — which you connect to via the internet — and reserve them for your own use, or just pay-as-you-go for the time you’re using them.

It allows businesses to benefit from powerful and expensive hardware, without the cost of purchasing, configuring, and maintaining that hardware. There’s essentially no limit to the number of virtual machines and servers you can rent, which means you can scale up and down rapidly to respond to peaks and troughs in demand, develop applications faster, and get much better value for money and flexibility than is possible from on-premises hardware.

Whereas, Amazon RDS is similar to Amazon EC2 but has been optimized for databases. We can run databases on Amazon EC2, although Amazon RDS has more features to automate many of the difficult and tedious tasks associated with relational database management such as backups, patching, failure detection, and recovery, albeit without some of the flexibility offered by Amazon EC2 Instances. While we’ll touch on AWS instance types and comparison of RDS options, this post focuses on Amazon EC2 Instances, which are more commonly used.

Fundamentals of AWS instances

The appropriate place to begin is with a description of an instance and an instance type. On AWS, an instance is a virtual machine that runs on a remote host machine (“hypervisor”) in a similar way to how a virtualized operating system runs on a desktop computer or server. The instance “type” is determined by the configuration of the hypervisor — which can be “General Purpose,” “Compute Optimized,” “Memory Optimized,” etc. Ultimately , the hardware used will dictate the memory, storage, compute capabilities, and performance of the virtual machine.

Various AWS instance types

AWS instances types are grouped together into families with several subcategories in each prodigy. These subcategories are based on the hardware on which they’re run, such as the number of virtual CPUs, memory (RAM), storage volume, and bandwidth capacity into and out of the instances.

The basic criterion towards AWS instance types selection should be based on the CPU and memory needs of different workloads and the network resources required. It’s important to choose the correct AWS instance types as there are considerable price differences between the different families of AWS instances and the different AWS instance types within those families. For example, instances with extreme memory and CPU capacities could be very expensive. Hence, it’s quite obvious to provision each instance perfectly at the point of deployment and monitor utilization thereafter as per our requirement.

The world of discrete AWS instance types and comparison of their competence

AWS instance types transform more frequently. As the cloud evolves and technology enhances, processors work faster and more efficient so we can do more with less. It’s always worth keeping an eye out for announcements from AWS about new generation instances in order to upgrade and maximize the benefits of operating in the cloud at your own pace.

Popular AWS instance genealogies

  • General Purpose (A1, T2, T3, T3a, T4g, M4, M5, M5a, M5n, M6g)
  • Compute Optimized (C4, C5, C5a, C5n, C6g)
  • Memory Optimized (R4, R5, R5a, R5n, R6g, X1, X1e, Z1d)
  • Accelerated Computing (P2, P3, F1, G3, G4)
  • Storage Optimized (D2, H1, I3, I3en)

The naming and numbering of different AWS instance types can be confusing. They consist of three parts, with each instance type typically given a letter (A, C, D, I, F, G, H, M, P, R, T, X) to denote its family, followed by a number that denotes its generation (1, 2, 3, 4, 5, 6). Each generation has a slightly different set of features. Some AWS instance types also have an additional letter to reflect how they’ve been optimized. For example, the “g” in T4g and M6g General Purpose instances indicates that the instances are powered by Graviton 2 processors, which are 40% more efficient than their predecessors.

Amazon RDS Instances are also based on processing power and memory requirements and are split into three classes: General Purpose (db.m4, db.m5, db.m6g), Memory Optimized (db.r4, db.r5, db.r6g, db.x1, db.x1e, db.z1d), and Burstable Performance (db.t2, db.t3), and also have multiple size options within each of the instance types. Generally speaking, the greater the instance size, the greater the cost.

AWS instance classification on the basis of comparison of purchasing options

As previously mentioned, there are considerable differences in pricing between families and instance types. Prices can change frequently so we won’t cover actual prices, only the primary purchasing options.

One of the main benefits of EC2 Instances are their flexibility and scalability. EC2 Instances can be purchased On-Demand whenever they’re needed. Instances can be provisioned and terminated as required and are billed by the hour that the instance is running. This option gives users maximum flexibility to scale up and down when it’s required, but it’s the most expensive way of purchasing AWS instances.

EC2 Reserved Instances allows it’s users to purchase instances for a finite period — one or three years — and are offered at a highly discounted rate, with the option of paying all upfront, partially upfront, or throughout the term. Businesses can purchase Standard Reserved Instances, or the more flexible, Convertible Reserved Instances, which due to their convertibility, don’t offer a significantly large discount.

The option also exists with AWS Savings Plans to commit to a specific monthly spend rather than a specific instance family. This provides even more flexibility than Convertible Reserved Instances, and the committed spend can be spread among AWS compute instances, Fargate , and some Lambda functions. Tilting towards the underlying hardware is shared with other customers, but it’s possible to pay for Dedicated Instances, which are instances that run on a virtual PC or hardware dedicated to a single customer and isolated from other customers´ instances at the hardware level.

In addition to the more generalized purchasing options, prices are dictated by the instance type, the type of Amazon Machine Instance used, the data transfer capability, the region the instance is provisioned in, and whether they’re EBS-optimized.

Thus , the above stats would surely help an individual choose the appropriate instance for their work purpose on the right time.

To launch the EC2 instance and mount an EFS file system -

  1. Open the Amazon EC2 console at
  2. Choose Launch Instance.
  3. In Step 1: Choose an Amazon Machine Image (AMI), find an Amazon Linux 2 AMI at the top of the list and choose Select.
  4. In Step 2: Choose an Instance Type, choose Next: Configure Instance Details.
  5. In Step 3: Configure Instance Details, provide the following information:
  • Leave Number of instances at one.
  • Leave Purchasing option at the default setting.
  • For Network, choose the entry for the same VPC that you noted when you created your EFS file system in Step 1: Create your Amazon EFS file system.
  • For Subnet, choose a default subnet in any Availability Zone.
  • For File systems, make sure that the EFS file system that you created in Step 1: Create your Amazon EFS file system is selected. The path shown next to the file system ID is the mount point that the EC2 instance will use, which you can change.
  • The User data automatically includes the commands for mounting your Amazon EFS file system.

6. Choose Next: Add Storage.

7. Choose Next: Add Tags.

8. Name your instance and choose Next: Configure Security Group.

9. In Step 6: Configure Security Group, set Assign a security group to Select an existing security group. Choose the default security group to make sure that it can access your EFS file system.

You can’t access your EC2 instance by Secure Shell (SSH) using this security group. SSH access isn’t required for this exercise. To add access by SSH later, you can edit the default security and add a rule to allow SSH. Or you can create a new security group that allows SSH. You can use the following settings to add SSH access:

  • Type: SSH
  • Protocol: TCP
  • Port Range: 22
  • Source: Anywhere
  1. Choose Review and Launch.
  2. Choose Launch.
  3. Select the check box for the key pair that you created, and then choose Launch Instances.

#aws #awscloud #EC2 #awsinstances #awsugjaipur

Follow us more on :- AWS User Groups ,AWS Identity, Amazon, Awsugsp !




(MAIT)Sophomore | CSE(Major) | Competitive Programmer | Google Cloud | Programming | Python Developer | Technical Writer | Open-Source Contributor | Enthusiast

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Software Development Process 6 Steps Of Critical Thinking

How we moved to CI/CD and improved our efficiency

ZKSwap Governance Proposal Voting Tutorial

Advertising another approach to Maintainable OOP

Eco-friendly Grafting & Chain Extension Pelletizing Series

Eco-friendly Grafting & Chain Extension Pelletizing Series

Sort Lists in List in Python

What is Git? Why is it Important?

iAllowance 3.0

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Nidhi Chaurasia

Nidhi Chaurasia

(MAIT)Sophomore | CSE(Major) | Competitive Programmer | Google Cloud | Programming | Python Developer | Technical Writer | Open-Source Contributor | Enthusiast

More from Medium

How Does the Instagram Algorithm Work in 2021?

Top 3 projects with the highest ROI index

My 2021 in Music

Why You Need Appointment SMS — and How to Get Started

Man in a waiting room, looking impatient.