Components of Proficy Historian for AWS
Proficy Historian for AWS contains the following components:
- Collectors: Collect tag data from various data sources. You can install collectors on multiple Windows machines. These machines can be on-premises or on a virtual private cloud (VPC).
- Clients: Include the following applications: You can use them to retrieve and analyze the data stored in Historian. You can install them on multiple Windows machines. These machines can be on-premises or on a VPC.
- AWS Network Load Balancer (NLB): Receives data read or write requests
from clients or collectors. If user authentication is needed, these requests are
sent to Proficy Authentication for authentication. Otherwise, these requests are sent to Data
Archiver.Note: The AWS NLB DNS name can be quite lengthy, for CIMPLICITY sources use the AWS IP address.
- Amazon Elastic Kubernetes Cluster (EKS): Hosts and maintains scalability
and high availability of the following components:
- Data Archiver: Intercepts requests from NLB. Sends user authentication requests to Proficy Authentication. Sends data read/write requests to Amazon Elastic File System (EFS).
- Proficy Authentication: An application that authenticates user credentials and grants access for Proficy applications.
- PostgreSQL: A database that stores user credentials.
- Amazon Elastic File System (EFS): Stores tag data in .iha files and configuration data in .ihc files, along with log files and buffer files. You can access these archive files and log files. It is fully managed, scalable, highly available, and durable.
- CloudWatch: Contains the logs generated by Data Archiver. You can also access the dashboard, which contains various widgets for your analysis and monitoring.
- CloudTrail: Contains the events generated by Data Archiver, containing information on the data consumption.