Availability Zones

Owned by Adaptavist ScriptRunner for Confluence Cloud
Last updated: Feb 08, 2024 by Ben Derr
1 min read

Within each AWS Virtual Private Cloud (VPC), multiple redundant servers are kept within different Availability Zones.

Search this space

Per AWS, "Each Availability Zone is engineered to be isolated from failures in other Availability Zones, and provide inexpensive, low-latency network connectivity to other zones in the same region." [Source]

Each Kubernetes cluster, for example production-cluster, is logically grouped within an AWS auto-scaling group (ASG), allowing for easy programmatic expansion when necessary, but are also housed in separate Availability Zones for improved redundancy. See Use of Kubernetes for additional details.

Nodes within a cluster are in 3 separate Availability Zones for additional resource isolation and redundancy. See Service Architecture for additional details.

See System Architecture for a full system architecture diagram and configuration explanation.

 

The content of the Tidepool Technical Documentation is licensed under a Creative Commons CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.