Creating an Environment

End-to-end guide: user accounts, SSH keys, VPCs, AMIs, and launching instances.

environmentvpcec2ssh

Overview

This guide walks through the complete workflow for creating a production-ready Hive environment.

Steps: 1. Create a user account 2. Import or create SSH keys 3. Create a VPC and subnet 4. Select and import an AMI 5. Launch EC2 instances 6. Connect via SSH 7. Monitor instance health

Instructions

1. Import SSH Key

bash

aws ec2 import-key-pair --key-name "hive-key" --public-key-material fileb://~/.ssh/id_rsa.pub

2. Create VPC

bash

aws ec2 create-vpc --cidr-block 10.200.0.0/16
export HIVE_VPC="vpc-XXX"

aws ec2 create-subnet --vpc-id $HIVE_VPC --cidr-block 10.200.1.0/24
export HIVE_SUBNET="subnet-XXX"

3. Import AMI

bash

./bin/hive admin images list
./bin/hive admin images import --name debian-12-x86_64
export HIVE_AMI="ami-XXX"

4. Launch Instance

bash

aws ec2 run-instances \
  --image-id $HIVE_AMI \
  --instance-type t3.small \
  --key-name hive-key \
  --subnet-id $HIVE_SUBNET \
  --count 1

5. Connect via SSH

bash

ps auxw | grep $INSTANCE_ID
# Look for: hostfwd=tcp:127.0.0.1:<port>-:22

ssh -i ~/.ssh/hive-key ec2-user@127.0.0.1 -p <port>

Troubleshooting

Instance stuck in pending

Check the Hive daemon and QEMU logs for boot errors:

bash

ls ~/hive/logs/
cat ~/hive/logs/daemon.log

Verify the AMI exists and architecture matches your host:

bash

aws ec2 describe-images --image-ids $HIVE_AMI

SSH connection refused

cloud-init takes 30-60 seconds to configure networking and SSH after boot. Wait and retry.

Verify the SSH port forwarding is active:

bash

ps auxw | grep hostfwd

Ensure you're using the correct key and port:

bash

ssh -i ~/.ssh/hive-key ec2-user@127.0.0.1 -p <port>