Platform AWS Deployment
Deploy the BigHammer umbrella chart (bighammer) on EKS. This page covers values preparation and Helm install — the final step after infrastructure, database bootstrap, secrets, and cluster add-ons are ready.
For a POC on single-node K3s (EC2) instead of EKS, see POC Setup (K3s on EC2).
Before you start
Complete these steps before running helm upgrade:
| Step | Action | Doc |
|---|---|---|
| 0 | EKS, RDS, AWS Secrets Manager, Route 53 | Infrastructure |
| 1 | Application DB schemas and grants | Prerequisites |
| 2 | Create / verify AWS Secrets Manager secrets | Secrets Manager Secrets |
| 3 | ESO, ALB Controller, TLS | Prerequisites |
| 4 | RabbitMQ broker (bhrabbitmq) | RabbitMQ Broker |
| 5 | Review chart version & download steps | Helm Releases — v1.0.12 |
Mirror chart and prepare values
Pull the chart from your mirrored registry (ECR) using OCI:
# Login to AWS ECR
aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin <aws_account_id>.dkr.ecr.us-east-1.amazonaws.com
# Pull the helm chart
# Pin the version from release notes (initial AWS catalog: 1.0.12)
helm pull oci://<aws_account_id>.dkr.ecr.us-east-1.amazonaws.com/bh-helm-release/bighammer \
--version 1.0.12
# Extract the chart
tar -xzf bighammer-1.0.12.tgz
cd bighammer
cp values-release.yaml ../values-<env>.yaml # edit all placeholders
See v1.0.12 Release for BH catalog OCI paths and prerequisites.
Values files
| File | Use |
|---|---|
values.yaml | Chart defaults, global.remoteSecrets, service toggles |
values-release.yaml | Sample customer overlay in the chart (placeholder account IDs, hostnames, IPs) |
values-<env>.yaml | Your per-environment overlay (copy from values-release.yaml) |
values-release.yaml uses fictional placeholders. Copy it to values-<env>.yaml in your deployment repository and replace every sample value with your target configuration.
Required global settings
| Path | Example (replace with yours) |
|---|---|
secretStore.name | aws-secret-store |
secretStore.region | us-east-1 |
awsRegion | us-east-1 |
image.repository | <aws_account_id>.dkr.ecr.us-east-1.amazonaws.com/ |
ingress.uiHostName | ui.dev.bighammer.ai |
ingress.aiAgentHostName | aiagent.dev.bighammer.ai |
ingress.certificateArn | arn:aws:acm:us-east-1:123456789012:certificate/uuid |
Run deployment command
Once your values-<env>.yaml file is ready and secrets are validated, run the following command to deploy the platform:
helm upgrade --install bighammer ./bighammer \
--namespace bh-control-plane \
--create-namespace \
-f values.yaml \
-f values-<env>.yaml
Check the status of the rollout:
kubectl get pods -n bh-control-plane -w