Autobase 2.12 adds Netdata dashboards, multi-AZ cloud deployment, and AWS Secrets Manager

Autobase, the open-source internal database platform for PostgreSQL, has released version 2.12 with substantial operational and security improvements. The update adds built-in monitoring dashboards powered by the Netdata agent, covering system metrics, PostgreSQL health, PgBouncer connection pooling, and table/index statistics. For cloud deployments, Autobase now automatically distributes PostgreSQL nodes across multiple Availability Zones on AWS, GCP, and Azure by default, improving resilience against single-AZ failures.

The release also introduces AWS Secrets Manager as an external secrets provider, enabling centralized secrets management. Security enhancements include credential redaction from logs, replacement of PGPASSWORD environment variables with secure password files, IMDSv2 enforcement on AWS EC2, and EBS encryption with AWS KMS key support. Reliability fixes address WAL archiving preservation during restores, pgBackRest race conditions, and etcd/DCS operations on dedicated hosts. New SSH jump host support allows management of clusters in private networks without direct server access.

Platform and operational changes in Autobase 2.12

• Monitoring integration: Built-in dashboards use the Netdata agent to expose system, PostgreSQL, PgBouncer, and table/index metrics without requiring a separate monitoring stack deployment.
• Multi-AZ topology: Cloud provisioning on AWS (PR #1732), GCP (PR #1738), and Azure (PR #1740) now defaults to cross-AZ node distribution, reducing single points of failure in cloud infrastructure.
• Secrets management: A new secrets role enables exporting and storing credentials in AWS Secrets Manager, moving away from local or environment-based secret handling.
• Security hardening: PGPASSWORD environment variables are replaced with secure password files, pgBackRest configuration details are filtered from logs, and IMDSv2 is enforced for AWS EC2 instances to mitigate metadata service abuse.
• Backup reliability: WAL archiving is preserved and unintended replica promotion is prevented during restore operations; persistent backup storage identifiers improve cluster lifecycle management.

Why it matters

For organizations running self-managed PostgreSQL instead of commercial DBaaS offerings, Autobase 2.12 narrows the operational gap by adding observability and resilience features that are typically platform-managed. The security improvements—particularly IMDSv2 enforcement, EBS encryption with KMS, and secrets manager integration—address common compliance requirements for enterprises deploying PostgreSQL on AWS. These changes strengthen Autobase as a viable open-source alternative for teams needing cloud-native database automation without vendor lock-in.