Transaction Monitoring Regions and Disaster Recovery
Availability Zones (AZs)
Within each AWS region, Transaction Monitoring infrastructure is deployed across multiple Availability Zones (AZs). This multi-AZ architecture follows AWS best practices for resilience and high availability. By distributing resources across physically separate data centres, Transaction Monitoring ensures that service interruptions in one AZ do not impact overall platform availability.
Disaster Recovery (DR)
Transaction Monitoring supports in-region disaster recovery through its multi-AZ setup. All data and application components are synchronized across AZs within the same region, enabling seamless failover in the event of an AZ outage. This design delivers an Always On, Active-Active-Active DR strategy for Transaction Monitoring customers.
Note: Transaction Monitoring does not support cross-region disaster recovery. All DR capabilities are confined within the same AWS region. In the unlikely event of a full region outage, recovery would require manual intervention and redeployment to a new region.
Environment and Region Alignment
Transaction Monitoring environments are not mapped to Fenergo CLM environments on a strict 1:1 basis. For example, all CLM EMEA1 environments connect to a single Transaction Monitoring EMEA1 environment.
Current Transaction Monitoring environments and their AWS regions:
- EMEA1: eu-central-1
- EMEA4: eu-north-1
- NAR1: us-east-2
- APAC1: ap-southeast-2
Each Transaction Monitoring environment is provisioned in its own AWS region, providing geographic separation and compliance with local regulations.
Summary
Fenergo Transaction Monitoring is architected for resilience and high availability, with environments aligned to specific AWS regions and deployed across multiple AZs. In-region disaster recovery is built-in, ensuring continuity of service for customers. For more details on Transaction Monitoring architecture or environment alignment, please contact your Fenergo representative.