On-Premises KTIO Network Block

aws · network diagram.

Diagrams.so

About This Architecture

On-premises KTIO network block connects to AWS via redundant IPSec/IKEv2 VPN tunnels through a Palo Alto gateway. The DRIV2 application polls data from four internal sources—CTS database (10.150.247.11:1433), HMI interface (10.162.2.135:443), Agilion cluster (10.162.32.11/.20/.12:4000), and Hastus system (10.184.57.6:8810)—while pushing processed data to Expert2 via SMB, Kerberos, and LDAP protocols. This architecture demonstrates secure hybrid connectivity for operational technology environments requiring low-latency data synchronization between on-premises industrial systems and cloud analytics platforms. Fork this diagram on Diagrams.so to customize IP ranges, add monitoring components, or adapt the VPN topology for your hybrid network design. Export as .drawio, .svg, or .png for network documentation and change management workflows.

People also ask

How do I design a secure hybrid network connecting on-premises operational technology systems to AWS using redundant VPN tunnels?

This diagram shows an on-premises KTIO network connected to AWS via Palo Alto VPN gateway with dual IPSec/IKEv2 tunnels for redundancy. DRIV2 polls data from four internal sources (CTS, HMI, Agilion, Hastus) and pushes to Expert2, demonstrating secure hybrid connectivity for OT environments.

On-Premises KTIO Network Block

AWSintermediateVPNHybrid CloudPalo AltoNetwork ArchitectureIPSec
Domain: NetworkingAudience: Network engineers managing hybrid cloud VPN connectivity
1 views0 favoritesPublic

Created by

February 24, 2026

Updated

February 25, 2026 at 3:13 PM

Type

network

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI