This guide helps you navigate ForgeMT configuration modules—from platform setup to integrations. Follow it to deploy ForgeMT correctly, understand module dependencies, and onboard tenant teams with clarity.
Start here if you’re deploying for the first time:
Module | Description |
---|---|
platform/forge_runners |
Top-level module. Provisions runners and wires EC2/EKS logic. |
platform/ec2_deployment |
Sets up EC2-based ephemeral runners. |
platform/arc_deployment |
Sets up EKS runners using actions-runner-controller. |
Used to create AWS primitives required by ForgeMT.
Module | Purpose |
---|---|
infra/eks |
Provisions EKS cluster for ARC |
infra/ecr |
Creates ECR repos for runner images |
infra/storage |
Creates S3 buckets for logs and metadata |
infra/ami_policy |
Grants permissions to use shared AMIs |
infra/ami_sharing |
Shares AMIs across regions/accounts |
infra/opt_in_regions |
Enables additional AWS regions |
infra/service_linked_roles |
Enables EC2 Spot functionality |
Module | Purpose |
---|---|
infra/budget |
Creates AWS budget alerts |
infra/billing |
Adds CloudWatch billing alarms |
infra/cloud_custodian |
Applies cleanup/governance rules |
Optional modules for observability, access, and compliance.
Module | Notes |
---|---|
integrations/splunk_* |
Set of modules for Splunk Cloud, secrets, dashboards |
integrations/teleport |
Enables audit/session capture via Teleport |
Item | Purpose |
---|---|
Secrets Reference | Documents required keys, formats, scopes |
Dependency Guide | Shows setup order across modules |
Ready-made configuration examples:
View all: Deployment Index
infra/
modules (VPCs, EKS, IAM, S3, etc.)platform/forge_runners