AWS - t2.micro instance EBS Volume size - amazon-web-services

I was trying to create t2.micro instance via AWS console.
I hope its free for one year, but it does not come with any instance storage.
So i wanted to add EBS Volume in this instance? is it free?
What is the maximum EBS volume i can add in t2.micro as free?
Model vCPU CPU Credits / hour
Mem (GiB) Storage
t2.micro 1 6 1 EBS-Only

30 GB of EBS is comes with the Free Tier. Go ahead use the 30 GB of EBS.
You can break it and use it either way want like 20 + 5 + 3 + 2 GB [ with magnetic or Genral Purpose SSD ].

Related

How do I lower ebs?

I've only just starting using ecs and it seems like ebs is sky rocking.I wanna stay within the free tier without worrying about this My question is how do i lower ebs?
I'm using terraform ecs module. I changed the root_block_device_size to 10
module "ecs_cluster" {
cluster_instance_root_block_device_size = 10
}
This is the library I'm using Ecs module link(Terraform)
It mentions this
cluster_instance_root_block_device_size number
Description: The size in GB of the root block device on cluster instances.
Default: 30
cluster_instance_root_block_device_type string
Description: The type of the root block device on cluster instances ('standard', 'gp2', or 'io1').
Default: "standard"
For my ecs i have changed the block device size to 10 not sure if i should mess around with gp2 or io1 to lower it
Thanks!
Update using this https://aws.amazon.com/ebs/pricing/ and by
putting my configuration and it seems like gp3 and lowering the gigabytes does lower the price....However it seems like doing 10gb cannot be initialized with Terraform so i started deploying it with 30gb and lowered it to 10gb and it seemed to have worked...
That screenshot is for I/Os. Those are reads/writes to the disk volume(s). That's not related to the size of the volumes. Changing it from 30GB to 10GB is not going to impact the I/Os metric at all.
I/Os are only charged on magnetic EBS volume types. If you switched to an SSD based EBS volume type, like gp2, you would not be charged for the I/Os.
The AWS Free Tier includes "30 GB of Amazon EBS: any combination of General Purpose (SSD) or Magnetic". So you could have up to 30GB of free gp2 volumes, which would be much faster than the standard magnetic volumes you are using now, and you would also not be charged for I/Os on those volumes.

How many EC2 instances can be created for free tier account

I am using AWS free tier to create EC2 instances(OS: Linux). Its' root volumes must be greater than snapshot size. As far as I know, it should be bigger than 8 GB for Linux EC2. But I only have 30 GB EBS free volumes size.
Does it mean I can create 3 Linux EC2(8+8+8 < 30 GB) maximally?
Is there any way to get around the limit size of 8GB? For example, I would like to create 5GB EC2(Linux), So I can create 6 EC2 instances(30GB / 5GB = 6) with Linux.
ADD Volumes pic:
You may create as many EC2 as you want, AWS will charge you by the time you keep them running.
If you check this link, you'll see that AWS calculates the EBS pricing considering the time you keep it running:
For example, let's say that you provision a 2000 GB volume for 12 hours (43,200 seconds) in a 30 day month. In a region that charges $0.10 per GB-month, you would be charged $3.33 for the volume ($0.10 per GB-month * 2000 GB * 43,200 seconds / (86,400 seconds/day * 30 day-month)).
Besides EBS, you must consider EC2 hours too. If you run X EC2 instances which support Free Tier by H hours, you won't be charged if X*Y < 750 in a month period. For instance, if you have 3 instances, the maximum time you should run them is 750 / 3 = 250 hours in a month.
About the EBS size, I've never tried to decrease EBS size, but you may find some articles that explain how to to that: link 1 and link 2.
You can calculate the prices using AWS Calculator.
To apply free tier, don't forget to enable the option on top FREE USAGE TIER: New Customers get free usage tier for first 12 month

AWS Tier Limit Alert

recently I recive this email with an alert from AWS EC2 instance (its an free tier elegible with T2.Micro). I really do not understand this alert since no content that has been uploaded to the server weighs more than several megabytes. Thanks for your help!
The email alert from AWS:
enter image description here
This alert is about Elastic Block Storage. This means it is related to the sum of provisioned disk capacity multiplied by the running time of your instances/volumes. To get more details how it is calculated, see here: https://aws.amazon.com/ebs/pricing/
30GB-Mo under free tier means: You could provision a drive with 30GB and let it run continuously for an entire month.
The warning indicates, that the sum of all provisioned storage of your instances and volumes is higher than 30GB.
Note: The actual data uploaded and/or how much is free, is irrelevant. So for example a micro instance with default settings counts 8GB towards your limit and it does not matter that the fresh Linux without any data is only a couple hundred megabyte.
i asked this in support, this is the answer
When calculating the charges for EBS volume storage, your charges
depend on the size of the volume you've provisioned and the length of
time the volume is provisioned in a month.
1) where that usage comes from? The most important thing to keep in
mind is that you are not billed for actual usage-- instead, you're
billed for the provisioned size of the volume. For example, if you
create a 1 TB volume and only use 1 GB of it in a month, you will be
billed for the full 1 TB.
To take another example, if you had a 31 GB volume that was only
active for 24 hours in the month of December (a 31 day month,
comprised of 744 hours), you'd only be billed for 1 GB-month. If you
had a 1 GB volume active for 744 hours in December, you'd be billed
the same amount.
2) how can i see it? If you'd like to look at a more in-depth report
of your EBS usage, you can download a usage report here:
https://console.aws.amazon.com/billing/home#/reports
The usage reports can be used to help figure out billing for EBS. Make
sure to change the usage value given in the report into GB-months,
since the data is presented in byte-hours. You can convert the data
into GB-months by dividing the figure presented in byte-hours by
1024^3, then divide this figure by the number of hours in the month.
You can also find information on EBS charges here
https://amzn.to/2BqeGlY
3) the 30GB EBS free tier is for each EBS instance or is the sum of
all the EBS that i could create? The EBS free tier limit is calculated
for the total number of volumes provisioned in your account and not
per instance. For example, if you simultaneously run a Windows
instance and a Linux instance with an attached EBS storage of 30GB
volume each, it will intuitively exceed your Free Tier limits, as the
total of the volumes would be 60GB.

Amazon Elastic Block Store and EC2 drive

I am fairly new with AWS(just have a free AWS EC2 instance to test out AWS stuff) so the question might sound silly.
Today I got a mail that my Amazon Elastic Block Storeage has reached 85% usage on my free AWS account which is about 25 GB of the allocated 30 GB.
From what I read today, Amazon EBS is a persistent store used for EC2 instances.
However I can see in my EC2 instance that df -h just show 2 GB usage and available disk as 28 GB as this is just my practice instance.
Am I missing some important piece of information here?
EBS devices are block devices.
This means the service does not know how much data you actually store on them -- it only knows how much storage space you allocated. So, the results of df -h don't matter. The actual size of the volume is all that matters -- that's the basis for billing. The rest of the space (that space you aren't current using) is still storing something, even it if's just 0's, but the service is unaware of what you've stored. (Other storage services like S3 and EFS bill for actual data stored, because they are not block storage services.)
Now, the free tier allows 30 gigabyte-months of EBS volume usage. You can use more than that, but this is the limit that's provided for free. You'll be billed for any more than this.
A gigabyte-month means 1 gigabyte of block storage space, allocated for 1 month, regardless of how you use it.
Also, 2 gigabytes of allocated storage for 15 days is 1 GB-month.
Also, 10 gigabytes of allocated storage for 3 days is 1 GB-month.
...etc.
The free tier, then, would allow you to have a 30 GB volume for 30 days, or a 60 GB volume for 15 days, or even a 900 GB volume... but you could have it for only 1 day. But to avoid continuing charges, such a volume must be deleted -- not just the files on the volume.
The warning message was correct. If you have a 30 GB volume in place for 26 days, then you have used 26 GB-months of storage, which is 86.7% of the free tier limit of 30 GB-months.
For anyone stumbling upon this in 2021:
Free Trial provides 750 Hrs of Amazon EC2 Linux t2.micro and 750 Hrs of Amazon EC2 Windows t2.micro per month. However, both of them will add in to the free 30GB EBS pool. So make sure the memories allotted to both the VMs sum up to 30 GB or less.
There are limits on the type and number of resources you can allocate for each account.
It sounds like in your case, you are allowed to create a total of 30GB of EBS volumes. Once you allocate an EBS volume, in your case 25GB, it counts against that limit, even if it isn't used.
There is a section in the EC2 console (near the top) called "Limits" that will show you what your limits are, and what you are using.
Most limits can be extended with a simple support ticket.

Which one is better, one 300GB EBS or three 100GB EBS?

When launching a new EC2 instance with EBS (especially the new C4 instance), which one is better? Assuming I need to provision 300 GB total.
1 single 300 GB EBS storage to get 900 IOPS (General Purpose SSD) or
3 EBS storage with 100 GB each and get 300 IOPS (General Purpose SSD) only for each storage?
Any idea?
Option 1 will give you faster performance and better reliability. With 3 EBS volumes you need to stripe them to make a single one and a failure on any of the three will result in a complete failure of all.