In Amazon MSK, the pricing documentation has mentioned that - You pay for the amount of storage you provision in your cluster.
But while creating the msk cluster, we have defined initial volume size per broker is 100gb, And our cluster has utilized only 50gb during a month.
So I have to pay for 100gb as I have defined, or I have to pay for 50gb used by cluster
You pay for the amount of storage you provision, not the amount of storage you use. As is clearly stated in the pricing documentation.
You provisioned 100gb of storage, so you will pay for 100gb of storage.
Related
Amazon EBS volumes are billed by the gigabyte-month (GB-month). With Amazon Elastic Block Store (EBS), you pay only for what you provision. Volume storage for all EBS volume types is charged by the amount of GB you provision per month until you release the storage.
There is so much confusion in these statements, and I wonder how exactly EBS is billed and what exactly is meant by the unit "GB-Month"? I could see this unit is also associated with Amazon Aurora storage pricing.
Links:-
https://aws.amazon.com/ebs/pricing/
https://aws.amazon.com/rds/aurora/pricing/
A GB-Month is 1GB of storage for 1 month.
100GB stored for 1 month = 100 GB-Months
100GB stored for half a month = 50 GB-Months
It's similar to the electricity concept of Kilowatt-Hours (1kWh = 1kW for 1 hour).
It seems that my EC2 usage limit is being reached rather quickly. I have deleted all of my EC2 instances and most of my S3 buckets, and none of my EC2 instances even exist in the terminated state. Are there any other services other than EC2 that use the EBS storage? Thanks in advance.
Amazon EBS is only used by Amazon EC2 instances. (Well, it is also used by Amazon RDS, but it shows up as an RDS charge, not EBS.)
We are currently about a third of the way through the month, so you'd want to be around 30% of usage.
The Amazon EBS snapshot usage is ahead of that (58%). If this worries you, then you can delete snapshots under the Snapshots section in the EC2 console. Amazon Machines Images (AMIs) also use EBS snapshots, so check the Images section too.
The amounts are "growing" because they are based on a month of usage. So, 1GB for 1 day is ~ 3% of the month's total.
However, there is little need to panic — EBS Snapshots are charged at 5c/GB/month, so at the current rate of usage you might be charged 10c.
There can be another possibility where you run an instance with EBS volumes 'not deleted' even after the termination of instance, it can accrue storage charges also. So delete those ones also in the 'Volumes' section of EC2 instance if its still unused.
I'm using the AWS free tier to run my EC2 t2.micro instance with 30GB EBS storage.
My question is - when the Free Tier time will end, how much I will pay in total for running my EC2 instance?
I understand that the EC2 payment is ~$100/year, but what about the storage it's using? A huge part of the 30GB is AWS programs and the Windows OS, so I will pay this storage in addition to the EC2 payment?
So the actual total bill will be $100 (EC2) + $18 (30GB of EBS)?
Amazon has a pricing calculator to help you determine monthly costs. For you example in the us-east-1 without any data transfer costs, your monthly fee will be $15.45. This includes $12.45 for the T2.micro Windows instance and $3.00 for 30GB of EBS storage.
Amazon Pricing Calculator
Please let me aware about the charges of ssd while all ec2 instances is reserved, then why $0.10 per GB-month is deducting?
I have reserved c4.2xlarge and m4.xlarge instances but still charges are continuous deducted from bill the heavy charge only for this below:
$0.10 per GB-month of General Purpose SSD (gp2) provisioned storage - US East (Northern Virginia)
For the saving of cost what can i do more? like above things are not happening.
It appears that your situation is:
You have purchase Reserved Instances for a c4.2xlarge and a m4.xlarge instance
You are seeing charges for Amazon Elastic Block Store (EBS) SSD storage
This is normal behaviour.
A Reserved Instance is a pre-payment (either monthly or annual) for Amazon EC2 capacity. When running an EC2 instance that matches the Reserved Instances, there is no hourly charge because the Reserved Instance has pre-paid for that usage.
However, the cost of Amazon EBS is not included with a Reserved Instance. The cost of an EBS volume is additional to your Amazon EC2 costs. This applies for all types of EC2 instances, whether or not they are being charged as Reserved Instances and whether they are Running or Stopped.
Some options to further save money:
Only create EBS disk volumes as large as necessary. You always pay for the full size of the volume, so unused space still costs money. You can always modify the volume to make it bigger in future.
Turn off instances when they are not required, at least for any instances not covered by your Reserved Instance purchases
If you are running additional instances, consider using Spot Pricing (but instances might be terminated if the spot price rises higher than your bid price)
I understand Amazon will charge per GB provisioned EBS storage. If I create AMI of my instance, does this mean my EBS volume will be duplicated, and hence incur additional cost?
Is there other cost charge in creating and storing an AMI (Amazon Machine Image)?
You are only charged for the storage of the bits that make up your AMI, there are no charges for creating an AMI.
EBS-backed AMIs are made up of snapshots of the EBS volumes that form the AMI. You will pay storage fees for those snapshots according to the rates listed here. Your EBS volumes are not "duplicated" until the instance is launched, at which point a volume is created from the stored snapshots and you'll pay regular EBS volume fees and EBS snapshot billing.
S3-backed AMIs have their information stored in S3 and you will pay storage fees for the data being stored in S3 according to the S3 pricing, whether the instance is running or not.
In this case, you will pay for the size of the storage used, instead of the storage provisioned. Snapshots will not store any empty blocks.
In short, yes, you will incur additional charges, but at a less rate, namely, EBS snapshot storage rate. Provisioned EBS is the 'live' HD that will be charged at $0.10 per GB per month if using standard SSD (gp2, USA east pricing for 2022 used throughout). And if you provisioned 50 GB, you will be fully charged for that 50 GB, even if you are only using 5% of it. The charges will incur even if you forget to attach to an EC2 instance. $5 per month in this case.
When you create an AMI, AWS will create a snapshot in the background. This snapshot is viewable under EBS Snapshots and will not be deletable as long as that AMI is in existence. You will get an error if you try to delete this snapshot. Snapshots cost less than 'provisioned' EBS at $0.05 per GB per month, and since snapshots ignore empty blocks, it will be shrunk to used size, so if you are only using 5% of 50GB, the snapshot should only be around 2.5 GB. $0.13 per month in this case. No other charges.
If you are creating a lot of these, it can get expensive very quickly, so some people save these AMIs into S3, which is cheaper than EBS snapshots. This is somewhat advanced and as far as I know, it can only be done via AWS CLI, and not in the console. You use a command called aws ec2 create-store-image-task and you have to specify the destination bucket name, and make sure permissions for S3, EBS and EC2 will all allow it. More detail at the official AWS documentation. This would reduce the cost to about $0.023 per GB per month. There are other changes relating to this method, i.e. EBS Direct API, but it is not much and you can look it up in the documentations.
Recently in November 2021, AWS released archived function for EBS snapshots, which allows you to archive your snapshots for a minimum of 90 days for $0.0125. You do have to pay $0.03 per GB for restoring the data. However, this is designed for EBS backups (e.g. daily backups using snapshots) and you cannot archive an EBS snapshot that is associated with an AMI. You will get an error: Failed to archive snapshot... snap-xyz is in use by ami-123.
Below is an excerpt of an actual AWS bill that will explain it in a visual sense.