Other Deployments: ThingWorx Foundation on AWS
ThingWorx can be deployed in cloud platforms, such as Amazon Web Services (AWS). Many AWS services are available to help with deploying ThingWorx and managing it over time.
Regions - Geographic areas where AWS resources are physically located.
Availability Zones (AZ) - Isolated locations within a region. Each region contains multiple availability zones to support high availability deployments.
Virtual Private Cloud (VPC) - Used for configuring logical network topology, defining sub networks, configuring routing tables, and assigning private IP ranges. Additionally, VPC allows for defining hardware VPNs between AWS VPC and on-premise IT infrastructure.
EC2 Computing instances - Virtual machines used to host key software components of the ThingWorx platform: ThingWorx Connection Server (if needed) and ThingWorx platform (main application).
Application Load Balancing (ALB) - Automatically distributes incoming application traffic across multiple Amazon EC2 instances. It enables you to achieve fault tolerance in your applications, providing the required amount of load balancing capacity needed to route application traffic.
Elastic File System (EFS) - Provides file storage systems that can be shared and accessed by multiple EC2 instances.
Reference Architectures
AWS Production Deployment
List of Components
Number of Components
AWS region
1
AWS VPC
1
AWS Application Load Balancer
1 (if using a Connection Server)
ThingWorx Connection Server
1 (optional)
ThingWorx Foundation Server
1
PSM
1
AWS EFS
1 (to maintain ThingWorx logs)
PostgreSQL
1
Large Production Deployment (non-HA)
List of Components
Number of Components
AWS Region
1
AWS VPC
1
AWS Availability Zones
1
Application Load Balancer
1
ThingWorx Connection Server
2
ThingWorx Foundation Server
1
PostgreSQL
1
InfluxDB (single-node)
1
Active-Active High-Availability Deployment
List of Components
Number of Components
AWS Region
1
AWS VPC
1
AWS Availability Zones
1
Application Load Balancer (ALB)
2 or 3 instances:
Route device traffic to Connection Servers.
Route user traffic between Foundation nodes.
Route traffic between InfluxDB data nodes.
ThingWorx Connection Server
Minimum of 2. 3 pictured.
ThingWorx Foundation Server
Minimum of 2. 3 pictured.
Ignite
Two options:
Embedded within Foundation processes.
2 or more separate nodes (depends on HA requirements).
AWS EFS
3:
One for each Foundation server to store and archive logs.
One shared ThingWorx Storage repository for Foundation nodes.
ZooKeeper
Minimum of 3. Should be in odd-numbered allotments.
InfluxDB Enterprise
5 (or more):
3 Meta nodes.
2 or more Data Nodes, with total count evenly divisible by replication factor.
Database
2 pg-pool nodes and 3 PostgreSQL nodes, spread across multiple availability zones.
ThingWorx AWS IoT Connector (End of Life)
The ThingWorx AWS IoT Connector has been moved to End of Life (EOL) with the 8.5.0 release of ThingWorx, as documented in the ThingWorx Connection Services Help Center.
Please consult prior versions of this document if working with older ThingWorx releases.
Was this helpful?