- 最新
- 最多得票
- 最多評論
Hello.
I think there is something wrong with the calculation method.
I thought that if you want to run it for 3 hours a day, 3 days a week, you need to make the following choices.
"Usage" is calculated as 9 because it runs 3 hours a day and 3 days a week.
If you would like to find out more about charges, we recommend that you open a case with AWS Support under "Account and billing".
Inquiries under "Account and billing" are free of charge.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
I was adding the daily figures under the EC2 specifications daily spike traffic and had the compute saving plan turned on by default. Still it should come to the same result. But its displaying a different figure. Also 9 hrs a week monthly comes to 36 hours. How is the 39 hours derived?
Also 9 hrs a week monthly comes to 36 hours. How is the 39 hours derived?
There aren't exactly four weeks in a month.
AWS will work out the figures as 9 hours per week => avg 9/7 hrs per day => 9/7 * 365 hrs per year => 9/7 * 365 / 12 hrs per month = 39.107
Got it. Thanks a ton.
相關內容
- 已提問 6 個月前
- 已提問 6 個月前
AWS 官方已更新 2 年前
The calculation is like this.
I think the usage of Daily spike is different. Daily spike is a method of calculation that assumes that spikes will occur, so I think it is a calculation method when increasing the number of instances to cope with spikes. I don't think this is the calculation method used when stopping EC2 on a daily basis.
Clear enough. Thank you.