Best Practices and Additional Resources
Post-Upgrade Checklist
- Database upgrade completed successfully to PostgreSQL 16
-
PGSSLMODE=require
environment variable configured - SSL connections verified and working
- Application starts without SSL errors
- Database operations working correctly
- SSL connection verified in logs
- Performance testing completed
- Backup verification completed
- Monitoring and alerting updated
- Documentation updated with new configuration
- Team trained on new setup
Security Best Practices
- Always require SSL connections: Set
PGSSLMODE=require
for all Azure PostgreSQL connections - Use Azure Key Vault: Store database passwords and sensitive configuration in Azure Key Vault
- Enable Azure PostgreSQL audit logs: Monitor database access and changes
- Network security: Use private endpoints when possible for Azure PostgreSQL
- Regular security audits: Monitor connection logs for SSL issues
- Backup encryption: Ensure backups are encrypted (enabled by default in Azure)
- Use Azure AD authentication: When supported, use Azure AD instead of passwords
- Implement proper RBAC: Use Azure RBAC for resource management permissions
Additional Resources
- Azure Database for PostgreSQL Documentation
- Azure PostgreSQL Flexible Server Major Version Upgrade
- Azure PostgreSQL SSL Configuration
- ToolJet Environment Variables Documentation
- Azure Kubernetes Service Documentation
- Azure Container Instances Documentation
- ToolJet Kubernetes AKS Setup
- ToolJet Azure Container Setup
note
Important Note: The PGSSLMODE=require
environment variable is mandatory for connecting to Azure Database for PostgreSQL Flexible Server. This ensures secure SSL/TLS encrypted connections are established and is a requirement for all Azure PostgreSQL databases.