Revisit Amazon Web Services re:Invent 2024’s biggest moments and watch keynotes and innovation talks on demand
Amazon IoT TwinMaker makes it faster and easier for developers to create digital twins of real-world systems such as buildings, factories, industrial equipment, and production lines. You pay for what you use and you are charged by the number API calls made, the number of entities in your systems, and the number of queries you execute. You can choose between basic, standard, and tiered bundle pricing plans depending upon the size and unique characteristics of your workloads
Unified data access API calls
Amazon IoT TwinMaker makes it easy for developers to build digital twin web applications by providing a unified data interface to various data stores. To read or write from these data stores, your web application will call the Amazon IoT TwinMaker unified data access APIs. Amazon IoT TwinMaker offers built-in connectors to data stores such as Amazon IoT Sitewise and Amazon Kinesis Video Streams, and you can also easily create connectors to other Amazon Web Services or third-party data stores. You pay for the number of unified data access API calls you make. The Amazon IoT TwinMaker unified data access APIs retrieve up to 20 KB of data per API call. If there is additional data to access, the API result will provide a link to the next 20 KB of data so you can call the access APIs again to retrieve it. For example, you might have a dashboard application that requests 30 KB of data to populate a chart. This means that your application will issue two Amazon IoT TwinMaker unified data access API calls to retrieve the required data. The unified data access APIs are GetPropertyValue, GetPropertyValueHistory, BatchPutPropertyValues.
Data Connectors
Amazon IoT TwinMaker provides a framework for you to easily create custom data connectors to use with Amazon Web Services or third-party data sources, such as Athena connector, Snowflake, and Siemens MindSphere. These data connectors allow your applications to call the Amazon IoT TwinMaker unified data access APIs to read from and write to the different data stores without needing to query each data source using their own individual API.
In addition to the charges for unified data access API calls, you will incur charges for running data connectors as Amazon Lambda functions. For more information about these charges, see the pricing page for Amazon Lambda.
TwinMaker Knowledge Graph
Entities
Amazon IoT TwinMaker provides tools for modeling devices, equipment, spaces and processes to build a knowledge graph. You can create entities in Amazon IoT TwinMaker that are virtual representations of your real-world systems, such as a furnace or an assembly line. You can also specify custom relationships between these entities to accurately represent the real-world deployment of these systems. You are charged per entity per month in your Amazon Web Services account.
Queries
TwinMaker Knowledge Graph enables customers to query the digital twins built using Amazon IoT TwinMaker. You can query for entities, their components, and properties. You can also query entities based on their relationships with each other. You are charged for the number of queries executed. The query API is ExecuteQuery.
Customers must be on standard or tiered bundle pricing plan to use TwinMaker Knowledge Graph. Details below.
Free Tier
As part of the Amazon Web Services Free Tier, you can get started with Amazon IoT TwinMaker for free. You can use up to 50 million data access API calls for free each month for your first 12 months using Amazon Web Services services. When your free usage expires, or if your application use exceeds the free tier, you simply pay the rates listed in the Pricing Table. Note that free usage does not accumulate from one billing period to the next.
Pricing Plans
Under this plan, you will be charged a fee per million unified data access API calls. This pricing plan is suitable when building a basic digital twin dashboard app. Note that in order to use the TwinMaker Knowledge Graph feature, you must switch to a standard or a tiered bundle pricing plan as outlined below.
Prices:
| Amazon Web Service China (Beijing) Region, operated by Sinnet | |
| Unified Data Access API calls | ¥11 per million calls |
Under the standard pricing plan, you will be charged a fee per million unified data access API calls, a fee per entity per month, and a fee per every 10K queries executed. We recommend this pricing plan to all customers starting their journey with Amazon IoT TwinMaker. Under this plan, you can scale your digital twins and use features like Knowledge Graph to query your digital twins and gain insights from it. You can switch to a basic pricing plan or a tiered bundle pricing plan, and it will take effect at the next billing cycle.
Prices:
| Amazon Web Services China (Beijing) Region, operated by Sinnet | |
| Unified Data Access API calls | ¥11 per million calls |
| Entities | ¥0.365 per entity per month |
| Queries | ¥3.65 per 10k queries executed |
Tiered bundles offer a fixed monthly price for the entity tier you are in. It includes all Amazon IoT TwinMaker features. We recommend this pricing plan for predictable workloads as it offers pricing simplicity and predictability in billing.
Entity tiers are defined by the number of entities in the tier. For example, Tier 1 spans 1 - 1,000 entities, and is suitable for pilot projects or a small industrial site. Tier 2 spans 1,001 - 5,000 entities and is suitable for an average sized industrial site or a building. Tier 3 includes 5,001 – 10,000 entities typically representing large manufacturing plants. Tier 4 is for extra-large digital twins with 10,001 -20,000 entities for projects like smart cities or campuses. Your entity tier is automatically determined based on the number of entities in your Amazon Web Services account. Each entity tier includes unified data access API calls and query executions up to a certain limit as displayed in the table below. Once API and query limits are exceeded, overage charges will apply as shown.
Amazon Web Services China (Beijing) Region, operated by Sinnet
| Entity Tier | Price | Pricing Unit | Usage Threshold | Overage Price |
| Tier 1 (1 - 1,000 entities) | ¥ 1600 | Per month | Up to 25M unified data access API calls | ¥11 per million calls |
| Up to 3.8M queries executed | ¥3.65 per 10k queries executed | |||
| Tier 2 (1,001 - 5,000 entities) | ¥ 4750 | Per month | Up to 60M unified data access API calls | ¥11 per million calls |
| Up to 9M queries executed | ¥3.65 per 10k queries executed | |||
| Tier 3 (5,001 - 10,000 entities) | ¥ 8000 | Per month | Up to 95M unified data access API calls | ¥11 per million calls |
| Up to 14.3M queries executed | ¥3.65 per 10k queries executed | |||
| Tier 4 (10,001 - 20,000 entities) | ¥ 14250 | Per month | Up to 160M unified data access API calls | ¥11 per million calls |
| Up to 24M queries executed | ¥3.65 per 10k queries executed | |||
| > 20,000 entities | Usage pricing or Contact us |
If the number of entities in your digital twin change, you will automatically move to the appropriate tier within the same month. Your monthly charge will be prorated to the days you are in each tier. There is a 3-month commitment required when you switch to tiered bundle pricing plan. If you switch to basic or standard pricing plan, the new pricing plan will take effect at the next billing cycle after the 3 month commitment is met. Note that you will lose access to advanced features like TwinMaker Knowledge Graph if you switch to the basic pricing plan. The digital twin applications using these features will be impacted.
Pricing Examples
All pricing examples are based on Amazon IoT TwinMaker deployment in Amazon Web Services China (Beijing) Region, operated by Sinnet, using standard or tiered bundle pricing plan with no Amazon IoT TwinMaker feature restrictions.
Example 1 - Small factory site
You own a small factory production site digital twin in Amazon IoT TwinMaker with 800 entities. You have stored IoT sensor data in time-series data store from the factory equipment. As part of your workspace, you upload 3D CAD as Amazon IoT TwinMaker resources into S3. The goal is to build and deploy a Digital Twin (DT) dashboard app to monitor production status. You are charged with the number of entities per month, the number of unified data access calls per month and queries executed per month. We will walk through the pricing calculation for this scenario below and provide a comparison between both the standard and tiered bundle pricing plans.
Unified data access API calls
You have one production floor dashboard that is visible to everyone and runs 24x7. There are 10 operators on the production floor, and each operator uses 5 dashboards during working hours to monitor production status. Operators keep dashboards running for 4 hours daily during working hours. Each dashboard (production and operator) is making data access API calls for 30 data streams every minute. 16 alarms refreshed every 10 seconds are displayed on production and operator dashboards. You are charged with the number of unified data access API calls that are calculated based on dashboards updates. We calculate the number of unified data access APIs calls for different types of dashboards refresh below.
- Production floor dashboard = Number of dashboards * Number of data streams per dashboard * reads per month = 1 dashboard * 30 data streams per dashboard * (60 reads per hour) * 24 hours per day * 30 days per month = 1.296M API calls per month
- Production floor dashboard alarms = Alarm reads per month = (3600 seconds per hour / 10 seconds per read) * 24 hour per day * 30 days per month = 0.259M API calls per month
- Operator dashboards = Number of operators * Number of dashboards * Number of data streams per dashboard * reads per month = 10 operators * 5 dashboards * 30 data streams per dashboard * (60 reads per hour) * 4 hour per day * 30 days per month = 10.8M API calls per month
- Operator dashboards alarms = Number of operators * reads per month = 10 operators * (3600 seconds per hour / 10 seconds per read) * 4 hour per day * 30 days per month = 0.432M API calls per month
- Total API calls = 1.296M + 0.259M + 10.8M + 0.432M = 12.787M API calls per month
- Data access charges = 17.63 * ¥11 = ¥193.93 per month
Entities
You are charged with a fee per entity per month.
- Entities charge = 800 * ¥0.365 = ¥292 per month
Queries
- Production dashboard queries = Number of active alarms * reads per month = 4 * (3600 seconds per hour / 10 seconds per read) * 24 hour per day * 30 days per month = 1.037M queries per month
- Operator dashboard queries = Number of operators * Number of active alarms * reads per month = 10 * 4 * (3600 seconds per hour / 10 seconds per read) * 4 hour per day * 30 days per month = 1.73M queries per month
- Queries charge = (103.7+173) * ¥3.65 = ¥1 009.96 per month
Amazon IoT TwinMaker monthly bill with the standard pricing plan = ¥193.93 + ¥292 + ¥1009.96 = ¥1495.89 per month
Amazon IoT TwinMaker monthly bill with the tiered bundle pricing plan = ¥220 per month
Note: you will be charged separately by Amazon IoT Sitewise to ingest, store, and read the time-series data and alarms; and by Amazon S3 to store and read the 3D CAD data. For more information about these charges, see the pricing pages for Amazon IoT Sitewise, and Amazon S3.
Example 2 - Warehouse
You built a digital twin for a warehouse building in Amazon IoT TwinMaker. The warehouse is a large space with 5,000 entities. You have stored time-series data in Amazon IoT Sitewise from the IoT sensors in the building. As part of your workspace, you upload 100 GB of 3D CAD files into Amazon S3. The goal is to build and deploy a DT dashboard app to monitor production status for the warehouse building. You are charged with the number of entities per month, the number of unified data access calls per month and queries executed per month. We will walk through the pricing calculation for this scenario below and provide a comparison between both the standard and tiered bundle pricing plans.
Unified data access API calls
You have two production floor dashboards that are visible to everyone and run 24x7. There are 15 operators on the production floor, and each operator uses 10 dashboards during working hours to monitor production status. Operators keep dashboards running for 4 hours daily during working hours. Each dashboard (production and operator) is making data access API calls for 30 data streams every minute. 40 alarms refreshed every 10 seconds are displayed on production and operator dashboards. You are charged with the number of unified data access API calls that are calculated based on dashboards update. We calculate the number of unified data access APIs calls for different types of dashboards refresh below.
- Production floor dashboard = Number of dashboards * Number of data streams per dashboard * reads per month = 2 dashboard * 30 data streams per dashboard * (60 reads per hour) * 24 hours per day * 30 days per month = 2.592M reads per month
- Production floor dashboard alarms = Number of dashboards * reads per month = 2 dashboard * (3600 seconds per hour / 10 seconds per read) * 24 hour per day * 30 days per month = 0.518M reads per month
- Operator dashboards = Number of operators * Number of dashboards * Number of data streams per dashboard * reads per month = 15 operators * 10 dashboards * 30 data streams per dashboard * (60 reads per hour) * 4 hour per day * 30 days per month = 32.4M reads per month
- Operator dashboard alarms = Number of operators * alarm reads per month = 15 operators * (3600 seconds per hour / 10 seconds per read) * 4 hour per day * 30 days per month = 0.648M reads per month
- Total data reads = 2.592M + 0.518M + 32.4M + 0.648M = 36.16M reads per month
- Data access charges = 36.16 * ¥11 = ¥397.76 per month
Entities
You are charged with a fee per entity per month
- Entities charge = 5000 * ¥0.365 = ¥1825 per month
Queries
You will use TwinMaker Knowledge Graph queries to troubleshoot operational issues from the dashboards above. We assume there are 10 out of 40 alarms are in active state at any given time during the month, and have queries associated with those alarms run automatically to generate the list of associated entities to enable users to understand the active alarms.
- Production dashboard queries = Number of active alarms * reads per month = 10 * (3600 seconds per hour / 10 seconds per read) * 24 hour per day * 30 days per month = 2.59M queries per month
- Operator dashboard queries = Number of operators * Number of active alarms * reads per month = 10 * 10 * (3600 seconds per hour / 10 seconds per read) * 4 hour per day * 30 days per month = 4.32M queries per month
- Queries executed = (259 + 432) * ¥3.65 = ¥2522.15 per month
Amazon IoT TwinMaker monthly bill with the standard pricing plan = ¥397.76 + ¥1825 + ¥2522.15 = ¥4 744.91per month
Amazon IoT TwinMaker monthly bill with the tiered bundle pricing plan = ¥4750 per month
Note: you will be charged separately by Amazon IoT Sitewise to ingest, store and read the time series data and alarms, and by Amazon S3 to store and read the 3D CAD data. For more information about these charges, see pricing pages for Amazon IoT Sitewise, and Amazon S3.
