AWS IoT SiteWise is a managed service that makes it easy to collect, organize, process, and monitor data from industrial equipment at scale to help you make better, data-driven decisions. You pay only for what you use, with no minimum fees or mandatory service usage. You are charged separately for usage of Messaging, Data Processing, Data Storage, Data Export, AWS IoT SiteWise Monitor, AWS IoT SiteWise Edge, and Alarms.
Pricing details
AWS IoT SiteWise Messaging
Messages transport equipment data and computed data to, from, and within AWS IoT SiteWise. Messaging is metered by the number of messages ingested and retrieved by querying or publishing. A message can be ingested through an application programming interface (API)—a method allowing two software applications to exchange information, or generated by a computation over equipment data. A message can also be ingested through AWS IoT SiteWise APIs, including APIs used by AWS IoT SiteWise Edge or by other application clients (e.g., BatchPutAssetPropertyValue, CreateBulkImportJob). A message can be retrieved when a property, such as a measurement of a sensor value, is published to AWS IoT Core as a notification or as a response to a query request.
Messages ingested through the API are metered in 1 KB increments. Messages published to AWS IoT Core are metered in 1 KB increments, and this operation does not incur any additional messaging charges from AWS IoT Core. Messages published in response to an asset property query request are metered for each set of up to 50 property values or every 4 KB of data contained in the message, whichever results in a higher count of messages. An interpolated asset property request is used to estimate and retrieve the values of missing data points in stored time series data. Messages published in response to an interpolated asset property query request are metered based on the number of property values retrieved from storage to compute each interpolated value. For example, when using the API to retrieve hourly linearly interpolated temperature data of a pump or a machine over a day, 48 property values will be retrieved from storage using 48 messages to compute 24 interpolated values.
Additional charges apply for GET requests made against your Amazon Simple Storage Service (Amazon S3) bucket when data results are retrieved from your cold tier. For more information about these charges, see Amazon S3 pricing.
AWS IoT SiteWise Data Processing
You can create production metrics such as Operational Equipment Efficiency (OEE) using mathematical and statistical computations in AWS IoT SiteWise. Data Processed is metered by the number of computations run.
Transforms and Metrics: You can use a built-in library of operators and functions in AWS IoT SiteWise to create two different types of custom computations—transforms and metrics. AWS IoT SiteWise continuously computes each transform and metric whenever the underlying data is updated.
Auto-computed Aggregates: AWS IoT SiteWise automatically computes a set of commonly used aggregates such as average, sum, and count over multiple time periods (e.g., one-minute, one-hour) for equipment data, transforms, and metrics. For each message ingested, these aggregates are metered as a single computation.
AWS IoT SiteWise Data Storage
Once data is in the cloud, AWS IoT SiteWise stores equipment and computed data in a managed time series database that automatically scales with your data usage and storage. AWS IoT SiteWise monitors the size of your storage continuously to determine your storage charges.
AWS IoT SiteWise Data Export
You can store data from measurements, metrics, transforms and aggregates in AWS IoT SiteWise cold storage tier. AWS IoT SiteWise stores data in cold storage tier that is older than your predefined hot storage tier retention period, including data that is ingested using BatchPutAssetPropertyValue and CreateBulkImportJob. Data in cold tier is stored as Amazon S3 objects in an S3 bucket in your account. You will be charged for the number of S3 objects created or updated by AWS IoT SiteWise to store data in cold tier.
Additional charges apply for storing exported data in Amazon S3 and for PUT requests made against your Amazon S3 bucket. For more information about these charges, see Amazon S3 pricing.
AWS IoT SiteWise Monitor
AWS IoT SiteWise Monitor provides managed web applications for interacting with operational data from devices and equipment that send data to AWS IoT SiteWise.
AWS IoT SiteWise Edge
AWS IoT SiteWise Edge provides data collection and processing capabilities in the SiteWise gateway for local applications. SiteWise Edge capabilities are offered through packs.
Data Collection Pack: This pack enables data collection from common industrial data sources and transferring it to the AWS Cloud. You can collect data from OPC-UA servers, Modbus servers, and over Ethernet/IP. You can transfer the collected data to Amazon S3, AWS IoT SiteWise, AWS IoT Core, Amazon Timestream, and Amazon Kinesis.
The Data Collection Pack is free.
Data Processing Pack: This pack enables the processing of the computations (transforms and metrics) with AWS IoT SiteWise asset models and visualizing them with SiteWise Monitor web applications on the SiteWise gateway. You can also interact with the data processed locally by the SiteWise gateway using the same REST APIs you use with AWS IoT SiteWise in the cloud.
A Data Processing Pack is charged at $200 per active gateway per month. A gateway is considered active in a month if it connects to the AWS Cloud to receive SiteWise Edge software configuration updates.
Note that you will be charged separately for any other AWS services that you use; refer to specific pricing for those services. You will also be charged separately for AWS IoT Greengrass, which is used by SiteWise Edge.
AWS IoT SiteWise Alarms
The Alarms feature allows you to set up, visualize, and manage rule-based alerts to assess equipment behavior and identify equipment performance issues. Alarms in AWS IoT SiteWise are supported through the Alarms feature of AWS IoT Events. You will incur charges for alarms you create in AWS IoT SiteWise through AWS IoT Events. See AWS IoT Events pricing for details.
You will incur charges in AWS IoT SiteWise for publishing messages to AWS IoT Events that are used to evaluate alarms. You will also incur charges in AWS IoT SiteWise for storing alarm states received from AWS IoT Events.
Pricing examples
-
Example 1
An industrial production line is sending data to AWS IoT SiteWise in the US East (N. Virginia) region. The production line includes 10 pieces of equipment, each of which reports one measurement every second. You configure AWS IoT SiteWise to collect this measurement data and upload to AWS. The monthly AWS IoT SiteWise charges are estimated as follows:Usage SummaryMessagingNumber of measurements per equipment = one measurement per equipment
Frequency of message ingestion = one message per second per measurement
Number of messages ingested in a month = one message / second / measurement * one measurement / equipment * 10 equipment * 86,400 seconds / day * 30 days / month = 25,920,000 messages per month
Total number of messages ingested per month = 25,920,000 messages per month = 25.92 million messages per month
Data Processing
Auto-computed aggregates
Number of aggregate computations per message = one computation per message ingested
Total number of messages ingested per month = 25,920,000 messages per month
Total number of aggregate computations per month = one computation / message * 25,920,000 messages / month = 25,920,000 computations = 25.92 million computations per monthTotal computations per month = 25.92 million computations per month
Data Storage
Equipment data
Number of measurement messages per month = 25,920,000 messages per month
Size of each message = 150 bytes per message (assuming each message ingested is 150 bytes)
Storage per month = 25,920,000 messages per month * 150 bytes / message * 1 GB / (1024^3 bytes) = 3.62 GB per month*Auto-computed aggregates
SiteWise stores all auto-computed aggregates. The storage used by auto-computed aggregates depends on the number of aggregates and time intervals over which they are calculated. In the example above, six auto-computed aggregates calculated over three time intervals (one-minute, one-hour, one-day) will result in 0.37 GB per month of data stored.Storage from auto-computed aggregates = 0.37 GB per month*
Total data stored per month = 3.62 GB (from Equipment data) + 0.37 GB (from Auto-computed aggregates) = 3.99 GB per month*
* This data reflects the data storage volume at the end of the first month.
Billing SummaryMessagingMessaging charges = $1.00 per million messages
Total messaging usage in a month = 25.92 million messages
Monthly charges for messaging = 25.92 million * $1.00 per million messages = $25.92 per monthData Processing
Data processing charges = $0.50 per million computations
Total computations in a month = 25.92 million computations
Monthly charges for computations = 25.92 million computations * $0.50 per million computations = $12.96 per monthData Storage
Total data stored at the end of the month = 3.99 GB per month
Average storage usage per hour during the month = 1.995 GB*
Monthly charges for storage = 1.995 GB * $0.30 per GB-month = $0.60 per month**
*Assuming storage has grown linearly from 0GB to 3.99GB by the end of the month, average storage usage would approximate 1.995 GB.
**Data that remains in storage from prior billing cycles will continue to be metered and billed accordingly
Total Monthly Bill
Monthly AWS IoT SiteWise charges = $25.92 + $12.96 + $0.60 = $39.48 per month
-
Example 2
On top of example 1, say you now also define one custom transform per measurement to do unit conversion (e.g., convert temperature from Celsius to Fahrenheit). The additional monthly usage and charges are estimated as follows:Usage SummaryMessagingNumber of metrics per equipment = one metric per equipment
Frequency of messages generated per metric = one message / minute / metric
Number of messages generated in a month = one message / minute / metric * one metric /equipment * 10 equipment * 1440 minutes / day * 30 days / month = 432,000 messages per monthAdditional number of messages ingested per month = 432,000 messages per month = 0.432 million messages per month
Data Processing
Custom metrics
Frequency of computation per metric = one computation / message * one message / second / equipment * one equipment / metric = one computation / second / metric
Number of computations per metric per month = one computation / second / metric * 86,400 seconds / day * 30 days / month = 2,592,000 computations per metric per month
Number of computations across all equipment per month = 2,592,000 computations / metric / month* one metric / equipment * 10 equipment = 25,920,000 computations = 25.92 million computations per monthAuto-computed aggregates
Additional number of aggregate computations per month = one computation / message * 432,000 messages / month = 432,000 computations = 0.432 million computations per monthAdditional number of computations per month = 25.92 million (from Custom metrics) + 0.432 million (from Auto-computed aggregates) = 26.352 million computations per month
Data Storage
Custom metrics
Additional messages ingested per month = 432,000 messages per month
Size of each message = 150 bytes
Additional storage per month = 432,000 messages / month * 150 bytes / message * 1 GB / (1024^3 bytes) = 0.06 GB per monthAuto-computed aggregates
Additional storage from auto-computed aggregates on custom metrics = 0.37 GB.Additional data stored per month = 0.06 GB (for Custom metrics) + 0.37 GB (from Auto-computed aggregates) = 0.43 GB per month
Billing Summary
Messaging
Additional messaging usage per month = 0.432 million messages
Additional monthly charges for messaging = 0.432 million messages * $1.00 per million messages = $0.43 per monthData Processing
Additional computations per month = 26.352 million computations
Additional monthly charges for computations = 26.352 million computations * $0.50 per million computations = $13.18 per monthData Storage
Additional data stored at the end of the month = 0.43 GBAverage additional storage usage per hour during the month = 0.25 GB*
Additional monthly charges for storage = 0.25 GB * $0.30 per GB-month = $0.08 per month***Assuming storage has grown linearly from 0GB to 0.43GB by the end of the month, average storage usage would approximate 0.25GB.
**Data that remains in storage from prior billing cycles will continue to be metered and billed accordingly
Additional Monthly Bill for custom metricsAdditional monthly bill = $0.43 + $13.18 + $0.08 = $13.69 per month
-
Example 3
On top of example 2, say you now also define one custom transform per measurement to do unit conversion (e.g., convert temperature from Celsius to Fahrenheit). The additional monthly usage and charges are estimated as follows:Usage Summary
Messaging
Number of transforms per measurement = one transform per measurement
Frequency of message ingestion per transform = one message / second / measurement * one measurement / one transform = one message / second / transform
Number of messages generated per month = 10 equipment * one measurement / equipment * one transform / measurement * one message / second / transform * 86400 seconds / day * 30 days / month = 25,920,000 messages per month
Additional number of messages ingested per month = 25,920,000 messages per month = 25.92 million messages per month
Data Processing
Custom transforms
Number of computations per month per transform = one computation / message * one message / second / measurement * one measurement / transform * 86,400 seconds / day * 30 days / month = 2,592,000 computations per month per transform
Number of computations across all equipment per month = 2,592,000 computations / month / transform * one transform / measurement * one measurement / equipment * 10 equipment = 25,920,000 computations per month = 25.92 million computations per month
Auto-computed aggregates
Additional number of aggregate computations per month = one computation / message * 25,920,000 additional messages / month = 25,920,000 computations = 25.92 million computations per monthAdditional number of computations per month = 25.92 million (from Custom transforms) + 25.92 million (from Auto-computed aggregates) = 51.84 million computations per month
Data Storage
Custom transforms
Additional messages ingested per month = 25,920,000 messages
Size of each message = 150 bytes
Additional storage per month = 25,920,000 * 150 bytes / (1024^3 bytes/GB) = 3.62 GB per monthAuto-computed aggregates
Additional storage from auto-computed aggregates on custom transforms = 0.37 GB.Additional data stored per month = 3.62 GB (for Custom transforms) + 0.37 GB (from Auto-computed aggregates) = 3.99 GB per month
Billing Summary
Messaging
Additional messaging usage per month = 25.92 million messages
Monthly charges for messaging = 25.92 million messages * $1.00 per million messages = $25.92 per monthData Processing
Additional computations per month = 51.84 million computations
Monthly charges for computations = 51.84 million computations * $0.50 per million computations = $25.92 per monthData Storage
Additional data stored at the end of the month = 3.99 GB
Average additional storage usage per hour during the month = 1.965 GB*
Additional Monthly charges for storage = 1.995 GB * $0.30 per GB-month = $0.60 per month***Assuming storage has grown linearly from 0GB to 3.99GB by the end of the month, average storage usage would approximate 1.995.**Data that remains in storage from prior billing cycles will continue to be metered and billed accordinglyAdditional Monthly Bill for custom transforms
Additional monthly charges = $25.92 + $25.92 + $0.60 = $52.44 per month
-
Example 4
To example 3, you also add graphs. Using your custom application, you create a dashboard consisting of two graphs to monitor your equipment performance. On one of these graphs, you are monitoring raw data for your measurement retrieved using the GETAssetPropertyValueHistory API. On the other graph, you are monitoring five-minute linearly interpolated data for another measurement retrieved using the GETInterpolatedAssetPropertyValues API. Your application refreshes these graphs every 30 seconds, and your graphs show data over a one-hour window. The additional monthly usage and charges are estimated as follows:Usage Summary
Messaging
Your SiteWise monitor dashboard automatically refreshes every five seconds to help ensure that you are visualizing data close to real time. Assuming that you are monitoring graphs over a one-hour window, whenever the dashboard refreshes, all data points plotted on that one-hour window get refreshed. So, for each graph showing a one-minute aggregate, 60 total data points get fetched upon every refresh through messages. As each of these messages can carry 50 data points, the total messages retrieved can be estimated as follows:
Number of messages retrieved per refresh per graph = ceiling ((60 data points / refresh / graph) / (50 data points / message)) = two messages per refresh per graph
Number of messages retrieved across all graphs per refresh = two messages / refresh / graph * 10 graphs = 20 messages per refresh
Number of messages retrieved across all users per month = (20 messages / refresh) * (one refresh / five seconds) * 3,600 seconds / hour * eight-hour shift / day / user * 30 days / month * five users = 17,280,000 messages per month
Additional number of messages retrieved per month = 17,280,000 messages per month = 17.28 million messages per month
SiteWise Monitor
Number of unique active users per month = five plant operators = five users per monthBilling Summary
Messaging
Additional messaging usage from SiteWise monitor per month = 17.28 million messages
Monthly charges for messaging = 17.28 million messages * $1.00 per million messages = $17.28 per monthSiteWise Monitor
SiteWise Monitor charges = $10.00 per active user per month
Number of active users per month = five users
Monthly charges for SiteWise Monitor = five users * $10.00 per active user per month = $50 per monthAdditional Monthly Bill for SiteWise Monitor
Additional monthly charges = $17.28 + $50.00 = $67.28 per month
-
Example 5
To extend example 4, you also add graphs using your custom application. Using your application, you create a dashboard consisting of two graphs to monitor your equipment performance. On one of these graphs you are monitoring raw data for your measurement retrieved using the GETAssetPropertyValueHistory API. On the other graph, you are monitoring five-minute linearly interpolated data for another measurement retrieved using the GETInterpolatedAssetPropertyValues API. Your application refreshes these graphs every 30 seconds and your graphs show data over a one-hour window. The additional monthly usage and charges are estimated as follows:Usage SummaryMessaging
For the one-hour graph showing the raw measurement data, with measurements coming in at one data point per second, 3,600 total data points get fetched from storage upon every refresh. As each of these messages can carry 50 data points, the total messages retrieved can be estimated as follows:
Number of messages retrieved per refresh = ceiling ((3,600 data points / refresh / graph) / (50 data points / message)) = 72 messages per refreshNumber of messages containing raw data retrieved per month = (72 messages / refresh) * (one refresh / 30 seconds) * 3,600 seconds / hour * 24 hours / day * 30 days / month = 6,220,800 messages per monthFor the one-hour graph showing the five-minute linearly interpolated measurement data, 12 interpolated values are returned, which means 24 messages (two messages per linearly interpolated value) get fetched from storage per refresh.Number of messages containing interpolated data retrieved per month = (24 messages / refresh) * (one refresh / 30 seconds) * 3,600 seconds / hour * 24 hours / day * 30 days / month = 2,073,600 messages per monthTotal additional number of messages retrieved per month = 6,220,800 (for graph showing raw data) + 2,073,600 (for graph showing interpolated data) = 8,294,400 messages per month = 8.29 million messages per month
Billing SummaryMessaging
Additional messaging usage per month = 8.29 million messages
Monthly charges for messaging = 8.29 million messages * $1.00 per million messages = $8.29 per monthAdditional Monthly Bill for graphs in your custom application
Additional monthly charges = $8.29 per month
-
Example 6
You configure a single SiteWise Edge gateway to monitor performance of a workcell with minimum dependency on the network. The workcell comprises 10 pieces of equipment. You model equipment in AWS IoT SiteWise with 10 transforms and two metrics (of one-minute intervals). You configure AWS IoT SiteWise to compute the transforms and metrics in the gateway, and forward the final result to the AWS IoT SiteWise cloud service for storage. You create a SiteWise Monitor dashboard to view the metrics for the workcell and configure it to run on the gateway.Usage SummarySiteWise EdgeNumber of packs Used:
One Data Collection Pack
One Data Processing Pack per month
MessagingFrequency of messages from transforms = one message per second per transform
Number of messages from transforms per month, per gateway = 10 transforms x one message per second x 86,400 seconds/day x 30 days = 25.92 million messages
Number of messages from one-minute metrics results per month, per gateway = two metrics x 1,440minutes per day x 30 days = 86,400 messages
Number of messages ingested into cloud per month = 25.92 million messages + 86,400 messages = 26.0064 million messages per monthData StorageSize of message from transforms or metrics = 150 bytes per message
Metrics and transforms data stored in the cloud per month. = Size of message x number of messages per month = 150/1 GB (1024^3 bytes) x 26.0064 M = 3.63 GB per monthBilling SummarySiteWise Edge = One Data Processing Pack x $200 per pack, per month = $200 per monthMessaging = 26 million messages x $1.00 per million messages = $26 per monthData Storage = 1.815 GB* x $0.03 per GB. Month = $0.05 per month*Assuming storage has grown linearly from 0GB to 3.63GB by the end of the month, average storage usage would approximate 1.815 GB.
**Data that remains in storage from prior billing cycles will continue to be metered and billed accordingly.
Total Monthly BillMonthly AWS IoT SiteWise charges = $200 + $26 + $0.05 = $226.05 per month -
Example 7
On top of example 3, you also configure AWS IoT SiteWise to export data from measurements, metrics, transforms, and asset definitions to an Amazon S3 bucket in your AWS account. The AWS IoT SiteWise data export charges are estimated as follows:Usage Summary
Data Export
We will first calculate the number of objects that will be exported for measurements, metrics, and transforms. AWS IoT SiteWise creates a new S3 object for each measurement, metric, or transform that has data in the system every six hours.
Number of objects per measurement, metric, or transform per month = 1 object / 6 hours * 24 hours / 1 day * 30 days / month
Number of objects per measurement, metric, or transform per month = 120 objects / monthTotal number of objects for measurements per month = 120 objects / measurement / month * 1 measurement / equipment * 10 equipment = 1,200 objects per month
Total number of objects for metrics per month = 120 objects / metric / month * 1 metric / equipment * 10 equipment = 1,200 objects per month
Total number of objects for transforms per month = 120 objects / transform / month * 1 transform / measurement * 1 measurement / equipment * 10 equipment = 1,200 objects per month
Total objects per month = 1,200 + 1,200 + 1,200 = 3,600 objects per month
Billing SummaryAdditional Monthly Bill for data export
Data export charges = $0.005 per thousand objects
Total objects exported per month = 3,600 objects
Additional monthly charges for data export = 3,600 objects * $0.005 per thousand objects = $0.018 per month* Additional charges apply for storing exported data in Amazon S3 and for PUT requests made against your Amazon S3 bucket. For more information about these charges, see Amazon S3 pricing.
-
Example 8
On top of example 1, you want to bulk import the last 60 months of historical data for that production line. You will use AWS IoT SiteWise CreateBulkImportJob API to ingest that data from another system to AWS IoT SiteWise.AWS IoT SiteWise will ingest data to the hot and cold storage tiers. Data timestamped after your defined hot tier retention period will be stored in the hot storage tier. Data timestamped prior to your defined retention period will be stored in the cold storage tier. For this pricing calculation we are going to assume that your hot storage tier retention period is 30 days. To learn more about AWS IoT SiteWise data storage, see Managing data storage. The AWS IoT SiteWise bulk import charges are estimated as follows:
Usage Summary
Messaging
AWS IoT SiteWise will import 1 month of data to the hot tier storage. From example 1, the total number of messages ingested per month = 25.92 million messages / month
Data Export
Number of objects per measurement, metric, or transform per month = 1 object / 6 hours * 24 hours / 1 day * 30 days / month
Number of objects per measurement, metric, or transform per month = 120 objects / month
Total number of objects for measurements per month for 10 equipment= 120 objects / measurement / month * 1 measurement / equipment * 10 equipment = 1,200 objects per month
AWS IoT SiteWise will export 59 months of data to the cold storage tier.
Total number of objects for 59 months of measurement data = 1,200 objects per month * 59 = 70,800 S3 objects
Billing SummaryMessaging
Messaging charges = $1.00 per million messages
Total messaging usage for 1-month historical data = 25.95 million messages
One time charge for bulk import of 1-month historical data to hot storage tier = 25.92 million*
$1.00 per million messages = $25.92Data Export
Data Export charges = $0.005 per thousand objects
Total objects exported for 59 months = 70,800 objects
One-time charge for bulk import of 59 months historical data to cold storage tier = 70,800*
$0.005 per thousand objects = $0.354
Refer to the AWS IoT SiteWise user guide, API reference and application guide for more information.
