Deploy the Web Admin Console by Launching through EC2
Before you begin
About this task
This topic describes how to deploy the Web Admin console using an Amazon Machine Image (AMI) by launching though EC2. You can also deploy it by launching from a website.
When you deploy the AMI, you will create a key pair (or use an existing one), which will be used later to connect the Web Admin console with the Historian server.
Procedure
- Log in to the AWS marketplace.
-
Search for Proficy Historian.
A list of products in Proficy Historian appears.
-
Select WebAdmin for Proficy Historian.
The product overview and other details appear.
-
Select Continue to Subscribe.
Your request for subscription is processed.
-
Select Continue to Configuration.
The Configure this Software page appears.
-
Enter values as described in the following table.
Field Description Fulfilment option Select 64-bit (x86) Amazon Machine Image (AMI). Software version Select 2023. Region Select the region on which you want to deploy the Web Admin console. For optimum performance, we recommend that you use the same region as the one on which you have deployed Proficy Historian for AWS. -
Select Continue to Launch.
The Launch this software page appears.
-
In the Choose Action field, select Launch
through EC2, and then select
Launch.
The Launch an instance page appears.
-
Enter values as described in the following table.
Field Description Name Enter a tag name for the instance. Instance type Select the instance type for the Web Admin console. Choose the type based on your data consumption. We recommend a minimum configuration of t3.medium. Key pair Select a key pair of the type RSA and format .pem, if you have one. If not, you can create a key pair. - Under Network settings, select Edit.
-
Enter values as described in the following table.
Field Description VPC Select the VPC on which you want to deploy the Web Admin console. Subnet Select the public subnet of the VPC on which you have deployed Proficy Historian for AWS. If you have used the default VPC, you need not provide the subnet details. -
Under Inbound security groups rules, enter the following
values for security group rules 1 and 2 respectively:
Type Protocol Port Range Source type SSH TCP 22 Select Custom, and enter the public IP address of the machine or network from which you want to access the Web Admin console. Provide a static IP address, or use the CIDR notation (for example, <IP address>/16). Custom TCP Rule TCP 9443 Select Custom, and enter the public IP address of the machine or network from which you want to access the Web Admin console. Provide a static IP address, or use the CIDR notation (for example, <IP address>/16). Or, if you want to access the Web Admin console only from your local machine, select My IP.
- As needed, configure storage and advance settings.
-
Select Launch Instance.
The Web Admin console is deployed.