This guide walks through the installation step by step.Documentation Index
Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
Use this file to discover all available pages before exploring further.
- AWS
- Kubernetes
Before You Begin
Make sure you have:- Your setup link (provided by us)
- AWS CLI installed and configured with appropriate permissions
- Terraform installed (v1.0+)
- Permissions to create VPCs, subnets, IAM roles, security groups, S3 buckets, and EC2 instances
Step 1: Open Your Setup Link
Open the setup link in your browser.Step 2: Select AWS and Your Region
Choose AWS as your environment. Select the AWS region where you want the infrastructure deployed. Pick the region closest to your users or the one that matches your compliance requirements.Step 3: Select Terraform as Your Install Method
Choose Terraform. The system generates a Terraform configuration tailored to your selections.Step 4: Download and Apply the Infrastructure Template
The first Terraform file creates your foundational infrastructure:- A VPC with public and private subnets
- IAM roles for the controller
- Security groups with minimal required access
- An S3 bucket for deployment state
Important: ReplaceReview the plan output carefully - it shows exactly what resources will be created in your account. The setup interface auto-advances when it detects the apply has completed.<YOUR_PROFILE>with the name of the AWS CLI profile configured for your dedicated deployment account. Using ambient credentials (e.g., from a different account) can cause errors. You can check your available profiles withaws configure list-profiles.
Tip: You can review the .tf file before applying. Everything is standard Terraform - no custom providers or opaque modules.
Step 5: Download and Apply the Controller Template
Once the infrastructure is in place, a second Terraform file becomes available. This creates the EC2 instance that runs the controller.Download the file, then run:- Runs in your private subnet (no public IP)
- Communicates outbound only - no inbound ports are opened
- Uses the IAM role created in the previous step
Step 6: Wait for the Controller to Come Online
After the controller template is applied, the instance boots and connects to our systems. The setup interface shows progress. This typically takes 2-5 minutes.Step 7: Configure Your Deployment
Once the controller is online, you move to configuration:- DNS - Choose a domain for the application. See DNS and Domains.
- Services - Select any service options relevant to your deployment. See Services.
- Secrets - Create any required credentials directly in your AWS account. See Secrets.
Step 8: We Deploy
After configuration is complete, we deploy the application into the environment you prepared. The controller handles the deployment automatically - you don’t need to do anything for this step.What Gets Created in Your Account
| Resource | Purpose |
|---|---|
| VPC | Isolated network for the deployment |
| Public subnet | Load balancer and NAT gateway |
| Private subnet | Controller instance (no public IP) |
| NAT gateway | Outbound internet access for private subnet |
| IAM roles | Permissions for the controller |
| Security groups | Network access rules (minimal) |
| S3 bucket | Deployment state storage |
| EC2 instance | Runs the controller |