Deploying Proficy Historian for AWS

To deploy Proficy Historian for AWS, you need a virtual private cloud (VPC), which allows you to deploy Proficy Historian into a virtual network that you have defined. For more information, refer to https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html.

Applying the license: You can use Proficy Historian for AWS with or without the Historian license. Accordingly, the following products are available in the AWS marketplace:
  • Bring your own license (BYOL): Use this product if you have the Historian for Linux license (or if you plan to get one). After you deploy Proficy Historian for AWS, apply the license.
  • Consumption-based: Use this product if you do not have the Historian for Linux license. A bill is generated based on your data consumption. For information on the pricing, refer to Access Pricing Information.
Deployment options:
  • By creating a new VPC: Use this option if you do not have a VPC, or if you want to create a separate VPC for Proficy Historian. If you choose this option, a new VPC is created, along with the public and private subnets (one for each availability zone), the NAT Gateway, and IGW. Proficy Historian for AWS is then deployed in that VPC.
  • By using an existing VPC: Use this option if you already have a VPC in which you want to deploy Proficy Historian for AWS as well. If you choose this option, Proficy Historian, along with the required resources, is deployed in your VPC.
After you deploy Proficy Historian for AWS, the following resources are deployed in the stack:
  • Elastic Kubernetes Service (EKS): Contains a cluster of EC2 instances.
  • Elastic File System (EFS): Stores the tag data and the tag configuration details.
  • Network Load Balancer (NLB): Receives requests from collector/client machines and directs them to the UAA service. The NLB DNS is also called the public IP address of the NLB. It is used to establish a connection between the Historian server and collectors/clients deployed on an on-premises machine or on a different VPC.
  • EC2 Instance: Contains the Data Archiver, Proficy Authentication, and PostgreSQL containers.
For more information on these components, refer to Deployment Architecture.