PRIMECLUSTER provides architectural patterns for ensuring the connectivity between a terminal directly operated by a user and the management view.
For smooth designing of a cluster system, choose the appropriate one from these architectural patterns.
The following are the architectural patterns for the connectivity with the Web-Based Admin View and the appropriate scenarios for each pattern.
Architectural pattern | Appropriate scenario | Note |
|---|---|---|
Ensuring connectivity with an instance for a client | Pattern using an instance for a client | An instance for the management view client must be deployed in the public subnet. |
Ensuring connectivity using a VPN connection | Pattern using a VPN connection | An additional device is required for a VPN connection. |
In the pattern using an instance for a client, to ensure the connectivity between a terminal directly operated by a user and the management view, prepare an instance for the management view client deployed in the public subnet. The system component for a VPN connection is not required and the configuration may be simple.
When selecting this architectural pattern, a user connects to a client of the management view via a remote desktop connection.
Figure 20.8 Ensuring connectivity with instance for client
In the pattern using a VPN connection, to ensure the connectivity between a terminal directly operated by a user and the management view, a VPN connection is used. No instances other than the management view are required in the VPC. This pattern is also secure because it does not use public subnets.
When selecting this architectural pattern, a terminal directly operated by a user is a client of the management view.
To provide a VPN connection, the VPN must be set or a device is required in the network where the terminal directly operated by a user is deployed.
Figure 20.9 Ensuring connectivity using VPN connection
