Single-Availability Zone Architecture
Cogynt may also be deployed to a single-AZ architecture, which does not support fault-tolerance or high availability. In this architecture, Cogynt is situated behind a network load balancer (NLB) and is in a single Availability Zone.
Single-AZ deployments are supported for both AWS and GCP.
Warning
Single-AZ is not suitable for running a production instance of Cogynt, and should only be used for evaluation purposes.
AWS Single-AZ Architecture
The components of an AWS single-AZ configuration are as follows:
- The internet gateway allows communication between an instance in your VPC and the internet.
- The NAT gateway in the public subnet enables the Amazon Elastic Compute Cloud (Amazon EC2) in a private subnet to access the internet.
- A network load balancer distributes web traffic across a single Amazon EC2 instance.
- The Amazon EC2 instance accesses data in an Amazon Elastic Block Storage (EBS) file system using a mount target.
- The Amazon EBS provides access to shared, unstructured data such as config, themes, and plugins.
GCP Single-AZ Architecture
The components of a GCP single-AZ configuration are as follows:
- The internet gateway allows communication between an instance in your VPC and the internet.
- The cloud NAT in the public subnet enables a VM instance in a private subnet to access the internet.
- Cloud load balancing distributes web traffic across a single VM instance.
- The VM instance accesses data in a persistent disk file system using a mount target.
- The persistent disk provides access to shared, unstructured data such as config, themes, and plugins.