In September 2026, GreenNode introduces updates across managed databases, Kubernetes and resource management. The theme this month is resilience and visibility: help teams keep critical workloads running through infrastructure incidents, and stay informed about their resources without constantly checking the Portal.

This month's highlights include Multi-AZ deployment for PostgreSQL Cluster in Ho Chi Minh City, PostgreSQL Cluster availability in the Hanoi region, Logging Control Plane for VKS in the HCM region, and proactive email notifications for vServer, vBackup and vStorage through vConsole.

Highlights at a glance

  • Deploy PostgreSQL Cluster across at least two Availability Zones in HCM, so your database keeps serving when one zone fails.
  • Run PostgreSQL Cluster in Hanoi, with Availability Zones HAN01-1A and HAN01-1B.
  • Collect and monitor Control Plane logs for VKS clusters in the HCM region.
  • Receive email alerts for important events on vServer, vBackup and vStorage, configured directly in vConsole.

vDB: More resilient PostgreSQL, now in two regions

PostgreSQL Cluster Multi-AZ in HCM

PostgreSQL Cluster now supports Multi-AZ deployment in the HCM region. Cluster nodes are distributed across at least two Availability Zones, so the cluster continues to serve requests if one zone experiences an incident.

   HCM03-1A                            HCM03-1B
┌──────────────────┐                ┌──────────────────┐
│ Primary (Writer) │ ─────────────→ │ Replica (Reader) │
│   Read / Write   │   Streaming    │ Read / Failover  │
└──────────────────┘   Replication  └──────────────────┘

The architecture consists of:

  • 1 Primary (Writer) node handling write operations.
  • Up to 9 Replicas (Readers) serving read traffic.
  • Automatic failover when the Primary becomes unavailable.

Multi-AZ can be configured directly at cluster creation. The VPC hosting the cluster must have DNS enabled.

For production databases behind customer-facing applications, a single-zone failure can mean downtime and manual recovery. Spreading nodes across zones reduces that risk without requiring teams to build and maintain their own replication and failover setup.

PostgreSQL Cluster now available in Hanoi

PostgreSQL Cluster (RDS) is now available in the Hanoi region, with Availability Zones HAN01-1A and HAN01-1B. It supports the same architecture as in HCM: 1 Writer, up to 9 Readers and automatic failover.

With both HCM and HAN available, teams can place databases closer to their applications and users in northern Vietnam. It also gives organizations more flexibility when planning data residency and multi-region architectures within Vietnam.

VKS: Logging Control Plane expands to HCM

Logging Control Plane for VKS lets teams collect and monitor logs from their cluster's Control Plane. The feature now supports the HCM region, in addition to the regions already available.

Control Plane logs help platform and DevOps teams investigate API server behavior, troubleshoot cluster issues and support audit requirements. Teams running VKS in HCM can now get this visibility without extra setup on their own.

vConsole: Proactive email notifications for vServer, vBackup and vStorage

Users can now configure email notifications directly in vConsole to stay informed about important events from vServer, vBackup and vStorage.

Instead of logging in to the Portal to check resource status, teams receive updates in their inbox as events happen. This helps operations teams respond sooner and keeps relevant stakeholders informed without extra manual checks.

What these updates mean

September's updates focus on keeping systems available and operations transparent:

  • Higher availability for databases: Multi-AZ PostgreSQL Cluster with automatic failover helps production databases survive zone-level incidents.
  • Wider regional coverage: PostgreSQL Cluster in both HCM and HAN gives teams more options for latency, data placement and multi-region design.
  • Better Kubernetes visibility: Control Plane logging in HCM supports faster troubleshooting and auditing for VKS clusters.
  • Proactive awareness: Email notifications bring important resource events to teams instead of requiring them to check the Portal.

For teams running business-critical workloads, the practical benefit is fewer surprises: infrastructure that tolerates failures better, and timely signals when something needs attention.

Technical documentation

Explore the following documentation to get started with the September 2026 updates:

Get started

Customers can log in to the GreenNode Portal to explore PostgreSQL Cluster Multi-AZ, PostgreSQL Cluster in Hanoi, VKS Logging Control Plane in HCM and email notifications in vConsole.

For architecture consultation or deployment support, contact the GreenNode team.

Frequently Asked Questions

What is PostgreSQL Cluster Multi-AZ?

It is a deployment mode where PostgreSQL Cluster nodes are distributed across at least two Availability Zones in HCM. If one zone has an incident, the cluster continues to serve requests.

How many nodes does a PostgreSQL Cluster support?

A cluster has 1 Primary (Writer) and up to 9 Replicas (Readers), with automatic failover.

What do I need before creating a Multi-AZ cluster?

The VPC hosting the cluster must have DNS enabled. Multi-AZ is configured at the cluster creation step.

Where is PostgreSQL Cluster available?

PostgreSQL Cluster is available in HCM and in Hanoi, with Availability Zones HAN01-1A and HAN01-1B. Multi-AZ mode is currently available in HCM.

Which regions support VKS Logging Control Plane?

The feature now supports HCM, in addition to the regions previously available.

Which services support email notifications in vConsole?

Email notifications currently cover vServer, vBackup and vStorage.

TagProduct updateVKSPostgreSQL