This Guidance demonstrates how to host AVEVA PI components in a resilient and highly available architecture on AWS, enabling advanced analytics. It utilizes Amazon Elastic Compute Cloud (Amazon EC2) to provision AVEVA PI components across multiple Availability Zones, helping to ensure fault tolerance and optimal performance. The Guidance showcases the migration of AVEVA PI systems to AWS and the configuration of PI components for resiliency and performance optimization. By implementing this Guidance, you can improve the resiliency, performance, and integration of your AVEVA PI implementation with modern analytic tooling on AWS.

Please note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • The PI Data Archive node stores critical business data on an EBS volume, enabling dynamic capacity scaling. Amazon CloudWatch monitors the unallocated space on the EBS volume, allowing administrators to proactively manage storage requirements. When low disk space is detected, data can be offloaded from the archive, or the EBS volume size can be increased on-demand.

    CloudWatch agent uploads message logs to CloudWatch, facilitating centralized logging and monitoring. CloudWatch metric filters and alerts seamlessly integrate with other AWS service notifications, streamlining operational visibility and incident response across the underlying infrastructure.

    Read the Operational Excellence whitepaper 
  • Direct Connect provides private networking between edge locations and the AWS Cloud over a standard Ethernet fiber-optic cable. Site-to-Site VPN encrypts traffic traversing the Direct Connect link, adding an extra layer of protection. Network Firewall provides granular control over network traffic entering the VPC, employing deep packet inspection, stateful protocol detection, source IP address filtering, and target domain name restrictions.

    This multi-layered approach, combining private networking, encryption, and advanced traffic inspection, enables a robust defense-in-depth strategy for securing critical Operational Technology (OT) workloads in the cloud.

    Read the Security whitepaper 
  • Fault Injection Service enables proactive testing of a system’s resilience by simulating various failure scenarios, such as node failures and network disruptions. This managed chaos engineering service facilitates regular fault injection experiments in non-production environments, helping identify and address potential configuration issues before they impact the business-critical production environment.

    Regular chaos testing with Fault Injection Service enhances the reliability of system deployment by helping ensure it can withstand and recover from various failure modes, minimizing the risk of unplanned outages and data loss incidents.

    Read the Reliability whitepaper 
  • Amazon EBS provides a range of configurable storage options, allowing you to select the appropriate volume type based on their workload's performance requirements, usage patterns, and cost considerations. For high-performance, large-scale deployments, the io2 Block Express volume type offers up to 256,000 IOPS and a maximum volume size of 64 TiB, catering to the most demanding workloads.

    By matching the EBS volume type to your specific needs, you can optimize performance and efficiency while minimizing unnecessary costs associated with over-provisioning or under-provisioning storage resources.

    Read the Performance Efficiency whitepaper 
  • AWS Backup provides a centralized and automated backup offering, eliminating the need for multiple backup tools and reducing operational overhead. By using automated backup scheduling, retention policies, and incremental backups, AWS Backup optimizes resource utilization and minimizes storage costs associated with backup and recovery operations.

    This streamlined approach to data protection not only simplifies backup management but also helps reduce the overall cost of maintaining a robust backup and recovery strategy, contributing to overall cost optimization efforts.

    Read the Cost Optimization whitepaper 
  • The PI Vision workload exhibits significant variability, with usage patterns fluctuating throughout the day, week, and based on the number of concurrent users. EC2 Auto Scaling dynamically adjusts the number of PI Vision nodes based on demand for optimal resource utilization.

    By automatically scaling the PI Vision node group up or down in response to these usage patterns, EC2 Auto Scaling minimizes energy consumption from idle or over-provisioned compute resources. This aligns your resource footprint with actual requirements, contributing to improved energy efficiency and reduced environmental impact.

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

[Content Type]


This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?