Skip to main content
Nuon can install Nuon on your cloud. Please reach out to sales.

​
Architecture

Nuon Cloud manages your BYOC control plane as an install — the same way your control plane will manage installs for your own customers. Upgrades, provisioning, and lifecycle operations are all driven remotely by Nuon.

​
AWS Account

You will need an AWS account. A VPC and other network infrastructure will be created during the installation. Ensure your user has 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.

​
Inputs

After configuring all dependencies, update your install inputs in the customer dashboard.

​
Authentication Configuration

If using the deprecated Auth0 integration, you will need to provide these inputs instead.

​
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

When provisioning the CloudFormation stack, provide these secrets:
The GitHub App PEM key must be base64 encoded because AWS CloudFormation doesn’t preserve newlines in text fields.To encode your PEM key:

​
Provision

Once all inputs and secrets are configured
  1. Return to your install in the Nuon dashboard
  2. Click Reprovision Install from the Manage menu
  3. Wait for the provision workflow to complete

​
Configure DNS (Optional)

To host your BYOC Nuon instance under a custom domain, configure DNS for your root domain to point to the Route53 Zone created in the sandbox. After the sandbox provisions, you’ll receive:
  • A Zone ID for your public domain
  • Nameserver records to add to your domain’s DNS
Create NS records in your domain’s DNS pointing to the Route53 nameservers provided.
See Creating a subdomain that uses Amazon Route 53 as the DNS service for detailed instructions.

​
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.