Exploring your post-installation options v1.3.4
Overview
Role: Infrastructure Engineer / Platform Administrator
Prerequisites
- Phase 1: Planning your architecture (Completed)
- Phase 2: Gathering your system requirements (Completed)
- Phase 3: Deploying your Kubernetes Cluster (Running and validated)
- Phase 4: Preparing your environment (Completed and validated)
- Phase 5: Installing Hybrid Manager (Completed & Verified)
- Administrator access to the Hybrid Manager (HM) Portal.
Outcomes
- A fully configured HM environment with security integrations, AI capabilities, and monitoring enabled.
Next Phase: Using Hybrid Manager
Now that the HM Control Plane is running, you can enable optional but critical integrations. While the platform is functional without these, configuring them now ensures your environment is production-ready for security, AI workloads, and observability.
Unlock AI capabilities: Complete GenAI Builder setup
Set up notifications (Observability)
Ensure your team is alerted to critical events (such as cluster failovers, backup failures, or capacity issues). HM allows you to configure notification channels globally or per project.
Supported channels:
Email
Webhooks (Slack, Microsoft Teams, generic JSON)
PagerDuty
Monitor external databases (Observability)
HM can monitor Postgres databases that it does not manage (examples: RDS, self-managed EC2, or on-prem instances).
To enable this, you must install the Beacon Agent on the external database host.
The agent collects metrics and logs, shipping them back to the HM control plane for centralized visualization.
Enable Migration Co-pilot
To use the AI-assisted Migration Co-pilot, you must apply specific secrets and configurations to the control plane.
This feature assists in analyzing and converting schemas from legacy databases to EDB Postgres.
Next steps
Your HM platform is now fully deployed and integrated. You are ready to onboard users and begin provisioning clusters.
Proceed to Using Hybrid Manager →