Is the Amazon Timestream pricing example wrong?

Hello TedOC,

I think the first month would be:
sum j**0.009864, j=1 to 25 == *$3.20
Because: 0.009864 = (10 GB/day ** $0.0000411/h ** 24h), and this adds up for 24 days (starting at day 4...28)

But $108 is really strange...

Greetings
Christian

Edited by: ChristianAchenbachUbix on Feb 26, 2020 7:08 AM

Hello TedOC,

oh, now I see: The retention of the magnetic store is 12 month. After a while you have to pay for the complete 12 month worth of data.

So: 10GB every day for the last 12 month = 3600 GB on magnetic disks * 0.03 = $108

Greetings
Christian

Edited by: ChristianAchenbachUbix on Feb 26, 2020 11:22 PM

Thanks. That might explain the cost of the final month after having used the system for a year. That doesn't seem to be what the example is trying to explain though.

Since Timestream is still not released two years after it was announced I don't know that the pricing really matters at this point.

Is there any update or guidance on ETA? It has indeed been almost two years since Timestream was announced. Back in 2018 it was one of the major reasons to start migration to AWS as we are processing gigabytes of smart parking sensor time-series data.

We are using RDS as a placeholder but the overheads are growing as data volumes build up!

https://www.nwave.io is waiting for Timrestream!
InfluxDB on EC2 is not the best recipe for 2020!