AWS IoT TwinMaker endpoints and quotas
The following are the service endpoints and service quotas for this service. To connect programmatically to an AWS service, you use an endpoint. In addition to the standard AWS endpoints, some AWS services offer FIPS endpoints in selected Regions. For more information, see AWS service endpoints. Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.
Service endpoints
To connect programmatically to AWS IoT TwinMaker, use an endpoint. If you use an HTTP client, you need to prefix control plane and data plane APIs as follows. However, it is unnecessary to add a prefix to AWS SDK and AWS Command Line Interface commands because they automatically add the necessary prefix.
-
Use the
apiprefix for control plane APIs. For example,api.iottwinmaker.us-west-1.amazonaws.com. -
Use the
dataprefix for data plane APIs. For example,data.iottwinmaker.us-west-1.amazonaws.com.
For more information, see Endpoints and quotas in the AWS IoT TwinMaker User Guide.
| Region Name | Region | Endpoint | Protocol |
|---|---|---|---|
| US East (N. Virginia) | us-east-1 |
iottwinmaker.us-east-1.amazonaws.com data.iottwinmaker.us-east-1.amazonaws.com iottwinmaker-fips.us-east-1.amazonaws.com api.iottwinmaker.us-east-1.amazonaws.com api.iottwinmaker-fips.us-east-1.amazonaws.com data.iottwinmaker-fips.us-east-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
| US West (Oregon) | us-west-2 |
iottwinmaker.us-west-2.amazonaws.com data.iottwinmaker.us-west-2.amazonaws.com iottwinmaker-fips.us-west-2.amazonaws.com api.iottwinmaker.us-west-2.amazonaws.com api.iottwinmaker-fips.us-west-2.amazonaws.com data.iottwinmaker-fips.us-west-2.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
| Asia Pacific (Mumbai) | ap-south-1 |
iottwinmaker.ap-south-1.amazonaws.com data.iottwinmaker.ap-south-1.amazonaws.com api.iottwinmaker.ap-south-1.amazonaws.com |
HTTPS HTTPS HTTPS |
| Asia Pacific (Seoul) | ap-northeast-2 |
iottwinmaker.ap-northeast-2.amazonaws.com data.iottwinmaker.ap-northeast-2.amazonaws.com api.iottwinmaker.ap-northeast-2.amazonaws.com |
HTTPS HTTPS HTTPS |
| Asia Pacific (Singapore) | ap-southeast-1 |
iottwinmaker.ap-southeast-1.amazonaws.com data.iottwinmaker.ap-southeast-1.amazonaws.com api.iottwinmaker.ap-southeast-1.amazonaws.com |
HTTPS HTTPS HTTPS |
| Asia Pacific (Sydney) | ap-southeast-2 |
iottwinmaker.ap-southeast-2.amazonaws.com data.iottwinmaker.ap-southeast-2.amazonaws.com api.iottwinmaker.ap-southeast-2.amazonaws.com |
HTTPS HTTPS HTTPS |
| Asia Pacific (Tokyo) | ap-northeast-1 |
iottwinmaker.ap-northeast-1.amazonaws.com data.iottwinmaker.ap-northeast-1.amazonaws.com api.iottwinmaker.ap-northeast-1.amazonaws.com |
HTTPS HTTPS HTTPS |
| Europe (Frankfurt) | eu-central-1 |
iottwinmaker.eu-central-1.amazonaws.com data.iottwinmaker.eu-central-1.amazonaws.com api.iottwinmaker.eu-central-1.amazonaws.com |
HTTPS HTTPS HTTPS |
| Europe (Ireland) | eu-west-1 |
iottwinmaker.eu-west-1.amazonaws.com data.iottwinmaker.eu-west-1.amazonaws.com api.iottwinmaker.eu-west-1.amazonaws.com |
HTTPS HTTPS HTTPS |
| AWS GovCloud (US-West) | us-gov-west-1 |
iottwinmaker.us-gov-west-1.amazonaws.com data.iottwinmaker.us-gov-west-1.amazonaws.com iottwinmaker-fips.us-gov-west-1.amazonaws.com api.iottwinmaker.us-gov-west-1.amazonaws.com api.iottwinmaker-fips.us-gov-west-1.amazonaws.com data.iottwinmaker-fips.us-gov-west-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
Service quotas
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Component type composition tree depth | Each supported Region: 5 |
Yes |
The maximum depth of a component type composition tree. |
| Component type composition tree size | Each supported Region: 50 |
Yes |
The maximum number of component types in a component type composition tree. |
| Component types per workspace | Each supported Region: 1,000 |
Yes |
The maximum number of unique component types per workspace. |
| Components per entity | Each supported Region: 30 |
Yes |
The maximum number of components that can be defined on one entity. |
| Depth of component type hierarchy | Each supported Region: 10 |
Yes |
The maximum depth of the component type hierarchy tree. |
| Depth of entity hierarchy | Each supported Region: 30 |
Yes |
The maximum depth of the entity hierarchy tree. |
| Entities per workspace | Each supported Region: 50,000 |
Yes |
The maximum number of entities allowed per workspace. |
| Number of SiteWise export resources per job | Each supported Region: 5,000 |
Yes |
The maximum number of SiteWise export resources per job. |
| Number of SiteWise import resources per job | Each supported Region: 5,000 |
Yes |
The maximum number of SiteWise import resources per job. |
| Number of TwinMaker export resources per job | Each supported Region: 100,000 |
Yes |
The maximum number of TwinMaker export resources per job. |
| Number of TwinMaker import resources per job | Each supported Region: 100,000 |
Yes |
The maximum number of TwinMaker import resources per job. |
| Number of metadata transfer jobs in queue | Each supported Region: 10 |
Yes |
The maximum number of PENDING metadata transfer jobs. |
| Parent component types per child component type | Each supported Region: 10 | No | The maximum number of multi-inheritance parent component types or "extendsFrom" relationships one component type can have. |
| Properties per component type or component | Each supported Region: 800 |
Yes |
The maximum number of properties that can be defined on a component type or added to any given component instance. |
| Scenes per workspace | Each supported Region: 100 |
Yes |
The maximum number of scenes within a workspace. |
| Size of the metadata transfer job import file | Each supported Region: 100 |
Yes |
The maximum size of the imported file (in MB). |
| Tags per resource | Each supported Region: 50 | No | The maximum number of tags that can be placed on any resource with an ARN (like workspace, entity, component type, etc.). |
| Workspaces in this account in the current Region | Each supported Region: 15 |
Yes |
The maximum number of workspaces in this account in the current Region. |
AWS IoT TwinMaker API throttling limits
This topic describes the maximum number of transactions per second (TPS) that can be made to AWS IoT TwinMaker API actions per AWS account.
Request rate for Model and Scene API operations limit: 10 TPS per AWS account.
Request rate for Data read and write API operations limit: 100 TPS per AWS account.
Note
The TPS limits apply to all regions, and are not adjustable.
