Deploy Proficy Historian for AWS in an Existing VPC

Before you begin

  1. Create a virtual private cloud (VPC), and make a note of the VPC configuration (that is, the IDs of the VPC, subnets, and so on). For instructions, refer to https://docs.aws.amazon.com/managedservices/latest/userguide/find-vpc.html and https://docs.aws.amazon.com/managedservices/latest/userguide/find-subnet.html.
  2. Ensure that you are in the region in which you want to deploy Proficy Historian for AWS. The following regions are supported:
    • Asia Pacific (Hong Kong)
    • Asia Pacific (Tokyo)
    • Asia Pacific (Seoul)
    • Asia Pacific (Mumbai)
    • Asia Pacific (Singapore)
    • Asia Pacific (Sydney)
    • Canada (Central)
    • Europe (Frankfurt)
    • Europe (Stockholm)
    • Europe (Ireland)
    • Europe (London)
    • Europe (Paris)
    • Middle East (Bahrain)
    • South America (Sao Paulo)
    • US East (N. Virginia)
    • US East (Ohio)
    • US West (N. California)
    • US West (Oregon)

About this task

This topic describes how to deploy Proficy Historian for AWS in an existing VPC. Alternatively, you can deploy Proficy Historian for AWS in a new VPC.

Procedure

  1. Log in to the AWS marketplace.
  2. In the list of products that appear, if you have the Historian for Linux license, select Proficy Historian for AWS.Or, if you want to use the consumption model, select Proficy Historian for AWS (Consumption Pricing).
  3. Select Continue to Subscribe.
    The terms and conditions appear.
  4. Select Continue to Configuration.
    The Configure this software page appears.
  5. Enter values as described in the following table.
    Field Description
    Fulfillment option Select CloudFormation Template.
    Software version Select 2023
  6. Select Continue to Launch.
    The Launch this software page appears.
  7. Under Deployment template, select Deploy Proficy Historian in the Existing VPC.
    The Quick create stack page appears.
  8. Enter values as described in the following table.
    Field/Section Description
    Stack name Enter a name for the stack. A value is required and must be unique. The value can include all alphanumeric characters and dashes. It must begin with an alphabetic character and cannot exceed 128 characters.
    VPC ID Enter the ID of the VPC on which you want to deploy Proficy Historian for AWS. For instructions on how to the find the VPC ID, refer to https://docs.aws.amazon.com/managedservices/latest/userguide/find-vpc.html.
    Private Subnets and Public Subnets IDs Enter the IDs of the two private and the two public subnets in your VPC. For instructions on how to find these IDs, refer to https://docs.aws.amazon.com/managedservices/latest/userguide/find-subnet.html.
    EKS cluster name Enter a unique name for the Elastic Kubernetes Service (EKS) cluster. A value is required, must be unique, and must be less than 28 characters.
    Instance type Choose an instance type based on your requirement. Our benchmarking results suggest that M5.Xlarge supports up to 15 million samples per minute. You can choose an instance of lower or higher capacity based on the rate of collection.
    TLS Configuration Provide the ARN of an SSL certificate. If you leave this field blank, we generate an openSSL certificate. However, we recommend that you provide a trusted certificate.
    Use Existing Proficy Auth and Proficy Config Hub Select Yes to use an existing instance of Proficy Authentication, and enter the URL below. Select No if you want to create a new instance of Proficy Authentication.
    URL of Proficy Authentication Provide the existing Proficy Authentication URL in the following format: https://<machinename>:443. For example: htttps://ec2-15-237-65-143.eu-west-3.compute.amazonaws.com:443
    Proficy Authentication Admin user secret Provide the admin user secret for Proficy Authentication. If using an existing Proficy Authentication, specify the admin user secret for the existing Proficy Authentication.
    Historian Admin User Password Provide a password to use as the admin secret and password for default users. The password must contain a minimum of eight characters, at least one uppercase letter, one lowercase letter, one number, and one special character. The password must start with a letter.
    Config Hub Admin User Password Provide the Configuration Hub user password. If not using an existing Configuration Hub instance, a password is required.
    CloudWatch Logging By default, the option to send logs to CloudWatch is enabled. This will allow you to send Data Archiver logs to CloudWatch; you can later access the logs and monitor them.

    And, the retention period is set to 30 days, after which the logs are deleted. If needed, you can change the retention period. We strongly recommend that you do not disable logging.
  9. If needed, you can choose to enable the client VPN endpoint for additional security.
  10. Select the check boxes to acknowledge the capabilities required by CloudFormation, and then select Create stack.
    Note: If you want to use windows Proficy Authentication with Historian on AWS 2024, also be sure to do the following:
    • Ensure that Windows VM or computer where Proficy Authentication is installed is accessible from the Internet.
    • When installing Historian Web Based Clients from the install media (ISO), specify the FQDN (Fully Qualified Domain Name). The following figure shows an example of how to specify the FQDN of a Windows EC2 machine.

    Be aware that the FQDN should be accessible from the public Internet.
    • If the user already installed Proficy Authentication on a Windows computer with Historian Web Based Clients without specifying a FQDN which is accessible from public Internet, then a re-install without purging databases of Historian Web Based Clients is needed. Specify public FQDN while re-installing.
    • While deploying Historian on AWS, in the CloudFormationTemplate parameters specify the following:
      • Yes for the 'Use existing Proficy Auth and Proficy Config Hub field
      • In the URL of Proficy Authentication area, the FQDN with the format: https://<FQDN>:443
      • The 'ProficyAuthentication Admin user' secret

    The stack is created, along with a VPC with two private and two public subnets.
    CAUTION: Do not update or delete the stack; you can lose data.

What to do next

  1. Apply the Proficy Historian for Linux license if you have one.
  2. Based on your requirement, install collectors.