After the installer reports success, do these checks before opening the installation to end users.

1. Sign in to the Configuration Service

Open the Configuration Service URL shown on the installer's Finish screen (typically https://<your-vam-host>/config).

  • Sign in with your OIDC credentials. If you used the bundled Keycloak, the installer's Finish screen shows the initial admin username and password — change the password on first login.
  • You should land on the Packages view. Confirm that the core VAM packages are listed and show Healthy.

If sign-in fails, see Troubleshooting → Cannot sign in.

2. Verify Cluster Health

From the Configuration Service, open Cluster in the navigation.

  • All nodes should show Ready.
  • The pod list should have zero pods in CrashLoopBackOff, Pending (longer than a few minutes), or ImagePullBackOff.
  • The Sanity check page (in the navigation) should show all green.

3. Confirm Storage

In Cluster → Storage, confirm:

  • The configured object storage backend (typically MinIO or an external S3) is reachable.
  • Free capacity matches what you provisioned. A multi-node install should show capacity aggregated across worker nodes.

4. Configure a Backup Destination

Backups are not configured automatically. Before going to production:

  1. Open Backup in the Configuration Service.
  2. Click Configure destination.
  3. Pick Local file share, S3-compatible, or Azure Blob and fill in the credentials.
  4. Run Test connection.
  5. Schedule a recurring backup (recommended: nightly).
  6. Manually trigger a first backup and confirm it completes.

See Backup and Restore for full details.

5. Smoke-Test an End-User Workflow

If your distribution includes sample data:

  1. Sign in to the VAM end-user UI (the public hostname without /config).
  2. Ingest a small media file.
  3. Confirm it appears in the asset list and the thumbnail generates.
  4. Search for it.
  5. Download / preview it.

If your distribution does not include sample data, pick a small representative file from your archive and repeat the steps above.

6. Save a Recovery Bundle

From the installer's main dashboard (re-launch vamctl.exe if needed), use Export configuration to save:

  • The wizard answers used at install time.
  • The cluster's kubeconfig.
  • A copy of the installation log.

Store this bundle in a safe location (not on the installer host). You will need it if the installer host itself fails and you need to manage the cluster from another machine.

Ready for Users

If all six checks pass, your installation is ready. Hand the end-user URL to your users and proceed to day-2 operations via the Configuration Service.