After the installer reports success, do these checks before opening the installation to end users.
Sign In to the Configuration Service
Open the Configuration Service URL shown on the installer's Finish screen. By default that is https://<vam-host>:30443/config.
- Sign in with your identity provider account.
- You should land on the Packages view. Confirm that the core VAM packages are listed and show Healthy.
If sign-in fails, see Identity Provider Setup > Troubleshooting Sign-In.
Verify Cluster Health
In the Configuration Service, open Cluster and Health. What the views show and what a healthy cluster looks like is in Cluster and Health.
- Failed should show zero.
- The pod list should have zero pods that stay in
Startinglonger than a few minutes. - The Health page should show all green.
Confirm Storage
On the Packages view, click Show all packages if system packages are hidden. Confirm that AIStor Object Storage shows Healthy.
Configure Backups
Backups are not configured automatically. Before going to production:
- Open Backup in the Configuration Service.
- Click Create Backup.
- In Target, select External S3 / MinIO or Network mount (PVC) and fill in the connection details. Schedules cannot use Download archive (small backups only).
- Click Create and confirm that the backup completes.
- Under Scheduled backups, click New schedule to schedule a recurring backup (recommended: nightly).
See Backup and Restore for full details.
Smoke-Test an End-User Workflow
The installer installs VAM and the Configuration Service. The applications your users work with are installed from the Configuration Service. See Managing Packages > Installing a New Package. Test each application you install:
- In the Configuration Service, open Packages and click the application's card.
- On the Overview tab, open the application from Access URLs.
- Run a typical task in it with a small, representative file from your archive.
Save the Cluster Credentials
If the installer host is lost, the cluster can only be managed from another machine if you still hold its credentials. Save them now.
- Re-launch
vamctl.exeand choose the Manage Cluster Contexts workflow. - Export the
kubeconfigandtalosconfigfor the new cluster. - Store them somewhere safe and not on the installer host, and treat them as secrets: a
kubeconfigwith cluster-admin rights is full access to the installation.
Keep a copy of the installation log files with them. Where the installer writes them is in Troubleshooting the Installer > Collecting Logs for Support.
Ready for Users
If all checks pass, your installation is ready. Hand the application URLs to your users and proceed to day-2 operations through the Configuration Service Overview.