Posts tagged #pgagroal
4 posts.
pgAgroal 1.4.5: Frontend TLS and Stricter HBA Security
pgAgroal 1.4.5 adds TLS for client connections, optional mutual TLS, stricter HBA source validation, and hardened Kubernetes deployment through Helm.
pgAgroal Enterprise 1.2.0: Verified TLS for Amazon RDS and Aurora
pgAgroal Enterprise 1.2.0 adds verified backend TLS (verify-ca / verify-full) so the pooler authenticates your RDS or Aurora certificate against a CA, not just encrypts it. It ships with a broad security-hardening batch and is live now on AWS Marketplace and GHCR.
Pooling was never the hard part
Putting a connection pooler in front of one database is easy, and that is why pooling gets called a solved problem. Running dozens of them the same way -- versions, certificates, config drift, upgrades across a Kubernetes fleet -- is a different problem entirely. A few opinions on why operating infrastructure is harder than installing it, and what a control plane should never do.
pgagroal 1.1.0 is out: what changed, what to migrate, how it's signed
Today we shipped elevarq/pgagroal:1.1.0, our container packaging of upstream pgagroal 2.1.0 — a feature release with a security-relevant migration. New AES-256-GCM vault encryption and a GCM-only management protocol mean operators must re-key the master and upgrade every pgagroal-cli in lockstep. Verifiable end-to-end with cosign signatures, SBOM, and SLSA provenance.