Deploy AI Command Center on AWS EKS
Use this workflow to coordinate an AI Command Center deployment after preparing the prerequisites. Deploy and validate Staging before promoting the approved release to Production.
1. Prepare the environments
The Customer Infrastructure team provisions Staging and Production EKS environments, databases, persistent storage, and optional ingestion dependencies. Configure networking, ingress, DNS, TLS, credentials, and required outbound connectivity. Confirm that each environment has independent configuration and data stores.
2. Obtain deployment artifacts
IntelliBuddies supplies the release-specific container image references, private registry access, and Helm deployment package through an agreed delivery mechanism. Obtain credentials securely and confirm the intended release before importing images.
Customers receive prebuilt images. Source repositories, Dockerfiles, and application build commands are outside the customer deployment delivery.
Helm package details
Obtain the following release-specific details from IntelliBuddies:
- Chart download location or OCI registry reference and chart version.
- Supported tooling and release compatibility.
- Container image repositories and release tags or digests.
- Environment configuration schema and sample values files.
- Required secrets and persistent configuration initialization.
3. Import and approve images in ECR
Customer DevOps pulls the supplied images from registry.ib-x.ai, imports them into customer-managed ECR repositories, and completes the required image security scanning and approval. Deploy the application images from ECR.
4. Configure the Helm release
Maintain separate Staging and Production configuration for the following areas:
| Configuration area | Environment-specific information |
|---|---|
| Release identity | Release name and Kubernetes namespace |
| Images | Customer ECR repositories and approved release references |
| Databases | Primary, archival, and optional ingestion connectivity |
| Secrets | Credentials and application master-key management |
| Storage | StorageClass, access mode, capacity, mounts, and permissions |
| Networking | Hostnames, ingress, TLS, service routing, and cluster DNS |
| Application services | Resource requests and limits, replicas, and external endpoints |
| Supporting services | Release-specific supporting services and optional dependencies |
5. Deploy and validate Staging
Deploy the approved release using the IntelliBuddies-provided Helm package and release-specific configuration guidance, complete application setup, and activate the Staging license. Verify application functionality, databases, persistence, and required connectivity using the verification checklist.
6. Promote the approved release to Production
Preferably promote the same approved container image versions validated in Staging. Apply Production-specific configuration, deploy the release, activate the Production license, and complete deployment acceptance before making the environment available for use.