By default, Hybrid Manager (HM) includes pre-configured secrets to facilitate a quick, out-of-the-box installation. However, these default secrets aren't intended for production use. For any live environment, you must create custom secrets to ensure your installation remains secure and unique.
HM secrets are categorized by installation scenarios. Depending on which installation scenarios you have enabled, you must configure the corresponding secrets below.
| Scenario | Feature | Key secrets | Docs |
|---|---|---|---|
core | Core platform (always enabled) | Bootstrap Fernet key, admin credentials, system database passwords | Core secrets |
ai | GenAI Builder | Fernet key, NVIDIA NGC credentials, HuggingFace token | GenAI Builder secrets |
analytics | Catalog | Confounding key | Catalog secrets |
migration | Migration Portal | DB accounts, Copilot HTTP/Metrics auth | Migration Portal secrets |
dbaas | Database-as-a-Service | None — No install-time secrets of its own. | — |
pgd | Distributed High Availability clusters | None — No install-time secrets of its own. | — |
marketplace | App marketplace | None — No install-time secrets of its own. | — |
To create the secrets for your selected scenarios, pass the same scenarios to edbctl with --scenario. See Create component secrets and Keeping your scenario selection consistent.