Fortifying Azure Database for PostgreSQL: Stop Intrusions in Their Tracks
summary
Covers concrete steps to lock down Azure Database for PostgreSQL: enable private endpoint (Feb 2024) to route traffic over the Azure backbone (multiple endpoints allowed, cannot switch connectivity mode after provisioning, extra cost), or keep public with firewall rules; configure passwordless via Entra managed identity for AKS + Spring Boot using workload identity and a federated credential, add the Spring Cloud Azure Starter JDBC PostgreSQL dependency, generate tokens for CI tooling like Flyway, and verify success by seeing the AKS token-exchange logs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:40Azure Database for PostgreSQL - Security
- 6:30Networking with Private Endpoint
- 13:30Access Management: Authentication and Authorization
- 16:13Authentication: Passwordless connection
- 21:52Authorization: Entra ID
- 27:02Access Management: Operational aspects
related talks
32mWhat makes Azure Database for PostgreSQL Great for Developers?
26mWhat Enterprises like about Azure Database for PostgreSQL - Flexible Server
56mSeamless Migration to Azure Database for PostgreSQL
27mAzure AD authentication with PostgreSQL Flexible Servers
57mDeveloping powerful and intelligent apps using the Azure managed PostgreSQL service
35mDeploying PostgreSQL to Azure with Bicep
31mBuild scalable and secure enterprise apps on OSS databases Q&A
50mSecuring PostgreSQL
