Timestream for LiveAnalytics magnetic storage cost

0

I can't understand why in last month's invoice I see an item indicating 'price per GB-Month of magnetic storage in Timestream 65.833 GB-Mo' but when checking with CloudWatch the metric MagneticCumulativeBytesMetered, I see that this metric starts from 11,000,000 and goes up to 406,000,000. From an estimate, using the 30-day average of the MagneticCumulativeBytesMetered metric, I should have about 84,875,866 bytes-month. Why do I see this discrepancy?

asked 15 days ago38 views
4 Answers
0

The discrepancy you're observing between your CloudWatch metric and the invoice can be explained by a few factors:

  1. Unit conversion: The CloudWatch metric MagneticCumulativeBytesMetered is measured in bytes, while the invoice reports storage in GB-Month. The conversion from bytes to GB involves dividing by 1,073,741,824 (1 GB = 1,024^3 bytes).

  2. Cumulative vs. average measurement: MagneticCumulativeBytesMetered is a cumulative metric that increases over time. The invoice, however, likely reflects an average or total usage over the month.

  3. Billing calculation: Amazon Timestream for LiveAnalytics calculates storage costs hourly. The magnetic store is metered in GB-month, which represents the cost of storing 1GB of data for one month.

To reconcile this:

  1. Convert the CloudWatch metric to GB: 406,000,000 bytes is approximately 0.378 GB.

  2. Consider the hourly measurements: Timestream emits this metric every hour. To get the GB-month value, you need to sum up all hourly measurements over the month and divide by the number of hours in the month.

  3. Calculate the average: The invoice's 65.833 GB-Mo likely represents the average storage used over the month, calculated from hourly measurements.

To verify, you could:

  1. Check CloudWatch metrics for each hour of the month.
  2. Sum these hourly values.
  3. Divide by the number of hours in the month.
  4. Convert to GB-month.

This should give you a value closer to what's on your invoice. If there's still a significant discrepancy, it would be advisable to contact AWS support for a detailed explanation of your specific usage and billing.
Sources
Metering and cost optimization - Amazon Timestream
Monitoring with Amazon CloudWatch - Amazon Timestream
Amazon Timestream Pricing – Time-Series Database – AWS

profile picture
answered 15 days ago
AWS
EXPERT
reviewed 15 days ago
0

This is the chart related to the MagneticCumulativeBytesMetered of the only Timestream database that contains data in my account: Enter image description here

answered 15 days ago
0

Hi,

Sorry for the concern. If you'd like, you can also reach out to our Account & Billing team via our Support Center, for assistance: go.aws/support-center. They'll be happy to review your account with you.

- Sage A.

AWS
EXPERT
answered 15 days ago
0

I asked to the support team but after a lot of questions and some incorrect answer they returned to me saying to pay for premium support or post a question here :( My last doubt is that the billing refers so same old timestream db or tables that I cannot see on the CloudWatch metric. Is this possible?

answered 2 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions