Architecture
On AWS, Nuon BYOC runs on an EKS cluster in a dedicated VPC. Ensure you have admin permissions, and that the account has not reached it’s quota limits for VPCs, EIPs, and Internet Gateways. The following regions have been tested and confirmed to support Nuon BYOC.- us-east-1
- eu-west-1
Nuon’s resource requirements are not compatible with AWS Free Tier. You will need a paid account.
Select installation method
Nuon supports provisioning the install stacks to AWS using either a Terraform module or a Cloudformation stack. Both options will provision the same architecture, and accept the same configuration. When using Terraform, provide them to the stack module using variables. When using Cloudformation, provide the inputs and secrets below manually through the AWS Cloudformation UI.When using using Terraform, we strongly recommend storing secret values in a secret store and passing them in using env vars or an ephemeral tfvars file.
- Terraform
- Cloudformation
main.tf
sh
Inputs
Authentication Configuration
GitHub Configuration
DNS Configuration
Database Configuration (Optional)
Adjust instance sizes for RDS, Temporal, and ClickHouse clusters if needed.Slack Configuration (Optional)
Provide these only if you created a Slack app in the Slack App section. Leave blank to disable the Slack integration.Secrets
The GitHub App PEM key must be base64 encoded to preserve newlines in text fields.To encode your PEM key:
Configure Telemetry Export (Optional)
Thenuon/<install-id>/telemetry-export-config is automatically generated by the stack, and grants the runner read access.
Update the secret to configure telemetry export to your own OTLP-compatible backend, starting with runner audit logs.
See Export Runner Audit Logs for the configuration reference, cloud-specific steps, and verification guidance.
Verify Installation
After successful provisioning, verify your installation is working by visiting these URLs.
You can also verify the API is responding by curling it directly.