This message was deleted.
# contributors
b
This message was deleted.
l
Hi @ripe-answer-8822. From what I can tell looking at the pricing, I think it makes sense to create separate cost components for each
operation
in the table. Then only add the relevant ones to the resource depending if it’s On-Demand or Provisioned.
From what I can tell here’s the cost component names we can have how I think they map to operations and usagetypes in the table you provided: if
stream_mode == On-Demand
add the following cost components: • On-demand stream -
OnDemandStreamHr
• Data ingested -
OnDemandDataIngested
• Data retrievals -
OnDemandDataRetrieval
• Enhanced fan-out data retrievals -
OnDemandEFODataRetrieval
• Data stored (after 24 hours)
OnDemandExtendedRetentionByteHrs
• Data stored (after 7 days) -
OnDemandLongTermRetentionByteHrs
if
stream_mode == Provisioned
add the following cost components: • Shared hour -
shardHourStorage
,
Storage-ShardHour
• PUT payload units -
PutRequest
• Extended data retention -
shardHourStorage
,
Extended-ShardHour
- I’m not sure about this one? • Long-term data retention -
LongTermRetentionByteHrs
• Long-term data retrieval -
LongTermRetentionDataRetrieval
• Enhanced fan-out data retrievals -
EnhancedFanoutDataRetrieval
• Enhanced fan-out -
ConsumerHour
,
EnhancedFanoutHour
👍 1