- Newest
- Most votes
- Most comments
Reserved Instances only apply to the compute instances, and not the attached storage.
Cost optimisation steps for EBS include:
- always use gp3 in preference to gp2, gives the same (or better) performance and is 20% cheaper
- only provision what you're going to use. If you provision 1TB but only use 100GB of it initially, you pay for the whole terabyte.
- nowadays there's almost never a use case for io1, unless you need a very large IOPS figure then a gp3 topped up with extra IOPS and throughput will still be cheaper (for some workloads I've found gp3 costs 10% of what the same spec of io1 costs)
- the only reasons to go for io2 is sub-millisecond latency, or extremely high IOPS figure. If your workload really does need these then you have to go with it, otherwise look at gp3 topped up with extra IOPS and throughput
Also, if you have volumes that you know are going to be idle for an extended period (although I doubt that, because if you are purchasing RIs you're going to want to run them as close to all the time as you can) then snapshot them and delete them. You can restore from the snapshots later when you need to use the volume again.
The comparison table here may be of use https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volume-types.html#vol-type-ssd
You are correct that Reserved Instance (RI) discounts are specifically for EC2 instances and do not apply to EBS volumes. RIs provide a discounted hourly rate for EC2 instances, offering significant savings compared to On-Demand pricing for steady-state workloads.
While RIs don't directly reduce EBS volume costs, there are a few strategies you can consider to optimize your EBS expenses:
-
Use EBS volume types appropriate for your workload: Choose the right EBS volume type based on your performance and cost requirements.
-
Leverage EBS Snapshots: Use snapshots to back up your data and only keep the necessary amount of EBS volume storage.
-
Delete unused EBS volumes: Regularly review and remove any unnecessary or orphaned EBS volumes.
-
Consider using instance store volumes: For temporary storage needs, use instance store volumes that come with certain EC2 instance types at no additional cost.
-
Monitor and optimize your EBS usage: Use AWS tools like CloudWatch to track your EBS utilization and identify opportunities for optimization.
-
Explore AWS Savings Plans: While not specific to EBS, Savings Plans can offer discounts on overall compute usage, which might indirectly help balance your total costs.
Remember, while these strategies can help manage EBS costs, the Reserved Instance discounts you're considering will only apply to the EC2 instance portion of your Amazon OpenSearch setup, not the associated EBS volumes.
Sources
Amazon EC2 Reserved Instances - Amazon EC2 Reserved Instances and Other AWS Reservation Models
Reserved Instances - Amazon EC2 Reserved Instances - AWS
Relevant content
- asked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
Reserved instances or savings plans are only for EC2, RDS or other services that use compute like Lambda. It does not apply to storage like EBS or S3. You have to pick the right volume type and size for you need. note different volumes have different IOPS.