Amazon Web Services (AWS) has launched the gp3 type EBS Volume and they are saying that it is 20% cheaper compared to gp2 types. Since the gp3 has a different pricing model compared to the gp2, I decided to go down this rabbit hole to see if the statement that gp3 is 20% cheaper than gp2 is always true.
My goal here is to confidently know that moving from a gp2 to gp3 will give us significant savings without the degraded performance.
TL;DR – Most of the time gp3 is cheaper than gp2. There are scenarios where the gp3 is more expensive than the gp2.
I wanted to investigate if the statement of Amazon Web Services (AWS) that “gp3 is 20% cheaper than gp2” is always true. That is why I’m creating this series of post to investigate when can we say that gp3 is really cheaper than gp2.
price is based on N. Virginia Amazon Web Services (AWS) Region.
The table in the Solid State Drive (SSD) part of the documentation only said something about Maximum Througput, but it never really say anything about what is the real Throughput or what are the conditions that affect the Throughput of gp2 volumes.
3000 IOPS free $0.05/provisioned IOPS-month over 3000 IOPS
Price of Throughput*
125 MiB/s $0.04/provisioned MiB/s-month over 125 MiB/s
* price is based on N. Virginia Amazon Web Services (AWS) Region.
For gp3 EBS Volumes, the throughput you set is sustained throughout its life unless you modify it.
Unlike the gp2 which has a Throughput that is dependent on the size of the volume and its burst credits, gp3’s Throughput is dependent on what you set, and how much are you willing to pay for the Throughput.
When I logged into my WordPress site via Google Chrome, I was warned with “The information you’re about to submit is not secure. Because the site is using a connection that’s not completely secure, your information will be visible to others.”
At first I did not understand why it was giving me this warning after more than year of setting up HTTPS in my site.