This directory contains supported AWS deployment assets for Hypeman.
| Deployment | Description | Path |
|---|---|---|
| Single node | One EC2 instance running Hypeman with nested virtualization enabled | single-node |
You need:
- An AWS account with permission to create EC2, IAM, CloudFormation, Lambda, Systems Manager, CloudWatch Logs, and related networking resources.
- Access to a region where the selected instance type is available.
- EC2 quota for the selected instance size.
- A VPC and subnet for the instance.
- An instance type that supports EC2 nested virtualization.
For the initial deployment path, use an Intel C8i, M8i, or R8i instance type. The default is chosen for a balance of cost and enough room to run useful Hypeman workloads.
Use CloudFormation when you want a guided AWS console flow.
Start with the single-node deployment:
Single-node CloudFormation deployment
Use CloudShell when you want a copy-paste command from the AWS console without installing local tools.
Single-node CloudShell deployment
Use Terraform when you want to review, version, and apply the AWS resources from your existing infrastructure workflow.
Single-node Terraform deployment
The single-node deployment uses an existing VPC and subnet. If public API access is enabled, restrict access to your current IP or a trusted CIDR.
The default path does not require SSH. Use AWS Systems Manager Session Manager for host access.
Each deployment README includes teardown instructions. Prefer deleting the CloudFormation stack or running terraform destroy instead of manually deleting individual AWS resources.