Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Registry Access Configuration

Why AWS CLI Is Required?

Hivel's Docker images are hosted on Amazon ECR regardless of your deployment target. You need AWS CLI configured with Hivel-provided credentials to pull them. No AWS account of your own is needed. Only the registry access Hivel provides.

Step 1: Configure AWS CLI

Run the following command on the host:

aws configure

When prompted, enter:

  • AWS Access Key ID: [Hivel-provided access key]

  • AWS Secret Access Key: [Hivel-provided secret key]

  • Default region name: ap-south-1

  • Default output format: json

Step 2: Verify AWS Credentials

Run:

aws sts get-caller-identity

Success: Returns a JSON object containing Account, UserId, and Arn Failure: "Unable to locate credentials" error means aws configure was not completed or saved to the wrong profile. Re-run aws configure and verify with cat ~/.aws/credentials.

Step 3: Authenticate to Hivel's Image Registry

Run:

Success: Output shows Login Succeeded Failure: See Registry pull failed in Troubleshooting

Alternative: Use Private Registry Mirror (Optional)

If your organization prohibits direct AWS ECR access, mirror Hivel's images into your own private registry (Harbor, Nexus, GitLab Registry, etc.). Update services/vm/docker-compose.yml and deploy.sh to reference your registry by changing the ECR_REGISTRY and AWS_REGION variables.

Back to Project Setup

Environment Configuration

Last updated