> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/architecture/cloud-infrastructure.md).

# Cloud Infrastructure

The Canton platform is deployed on a managed Kubernetes infrastructure designed for scalability, reliability, and ease of management. The architecture supports flexible database options, automated provisioning, comprehensive observability, and efficient traffic management.

<div data-with-frame="true"><figure><img src="/files/4lNjNBngMaILFFZ1aOZF" alt=""><figcaption><p>Cloud Infrastructure</p></figcaption></figure></div>

## Infrastructure

Canton nodes are hosted on AWS EKS, providing a scalable and managed Kubernetes environment that simplifies cluster operations and enhances reliability. While the reference setup runs on Amazon EKS, it is fully portable to Microsoft Azure (AKS), Google Cloud (GKE), or on-premises Kubernetes/OpenShift.

## Database

PostgreSQL can be deployed either **inside the Kubernetes cluster**, for tight coupling and simpler management, or **externally via a managed service** such as Amazon RDS, for improved scalability, automated backups, and managed maintenance.

## Deployment

The infrastructure is provisioned and managed using Terraform, integrated into an automated deployment pipeline to ensure consistent, repeatable, and auditable infrastructure changes.

## Ingress

Traefik serves as the ingress controller, managing incoming traffic with support for dynamic routing, load balancing, and TLS termination.

## Observability

Observability is implemented using **Grafana, Prometheus, and Loki**, providing a full-stack view of system health, performance, and events. This setup enables operators to monitor, analyze, and troubleshoot the system effectively. Key aspects include:

**Metrics collection and visualisation.** Prometheus collects detailed metrics from Canton nodes, databases, and supporting infrastructure. Grafana dashboards provide real-time visualisation, enabling insight into transaction throughput, node health, latency, and resource utilisation. Canton-specific dashboards include views for participant nodes, synchronizer nodes, transaction processing rates, and ledger state.

**Centralised logging.** Loki aggregates logs from all Canton components, including participants, synchronizers, and connectors. Centralised logging ensures errors, warnings, and system events can be traced quickly. Logs are searchable by node, timestamp, or component.

**Alerting and notifications.** Prometheus Alertmanager provides automated alerts based on defined thresholds or anomalies. Typical alerts cover node failures, high transaction latencies, resource exhaustion (CPU, memory, disk), and replication issues. Alerts can be routed to email, Slack, PagerDuty, or other incident management systems.

**Custom Canton dashboards.** Grafana dashboards are customised for Canton deployments to provide domain-specific views such as participant node performance, consensus progress, transaction conflict rates, and network latency between nodes.

**Historical analysis and reporting.** Collected metrics and logs are retained for historical analysis, enabling trend detection, capacity planning, and post-incident review. Operators can correlate metrics and logs to understand performance bottlenecks and optimise node configuration.

{% hint style="info" %}
The CatalyX console links directly into Grafana from the Validators and Applications lists, and from the validator Summary tab. See [Grafana Links](/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/grafana-dashboards.md).
{% endhint %}

***

## Reference services and backup

The table below lists the AWS services used in the reference deployment and how each is backed up. Equivalent services apply on other cloud providers.

<table><thead><tr><th width="200">Service</th><th width="240">Type</th><th>Backup</th></tr></thead><tbody><tr><td>EKS</td><td>Managed Kubernetes service</td><td>Cluster configuration stored as a Terraform repository</td></tr><tr><td>EC2</td><td>Compute</td><td>EBS snapshots</td></tr><tr><td>Secrets Manager</td><td>Secrets management</td><td>Secrets replicated across multiple regions</td></tr><tr><td>RDS (PostgreSQL)</td><td>Managed database service</td><td>RDS automated backup</td></tr><tr><td>EBS</td><td>Storage</td><td>EBS snapshots</td></tr><tr><td>Route 53</td><td>DNS</td><td>—</td></tr><tr><td>NLB</td><td>Network load balancer</td><td>—</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/architecture/cloud-infrastructure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.