Skip to main content
This quick start guide explains how to use Tensor9 to deploy your Terraform/OpenTofu (TF) app as a private appliance. As you follow this guide, you will:
  • Set up a Tensor9 control plane in your AWS account and bind a TF workspace as the origin stack for your app.
  • Test your app running in an appliance.
  • Release infrastructure changes.

Prerequisites

  • Send an email to [email protected] and request an API key. You must have an API key to complete the quick start.
  • Create an AWS account for Tensor9. We will refer to this as the Tensor9 AWS account. Important:
    • Your Tensor9 AWS account should be a dedicated AWS account used only for Tensor9. This reduces the risk of conflicts between your app deployed in a Tensor9 appliance and any other software, infrastructure, or resources you might have in a general-purpose AWS account.
    • Your Tensor9 AWS account must be located in a United States region. Support for non-US regions will be available in the near future.
  • Install AWS CLI in your environment, and set up an AWS CLI profile that has admin permissions to your new AWS account.

Install OpenTofu or Terraform

In your environment, you’ll need to install Terraform/OpenTofu CLI. This guide assumes you are using OpenTofu and uses the tofu command throughout.

Install Tensor9 CLI

Install the tensor9 CLI via Homebrew (recommended):
Alternatively, install via the install script:
Then set your Tensor9 API key:
Note: An API key is required. If you do not have an API key, send email to [email protected] to request one.

Set up a Tensor9 control plane and create a new app

  1. Set up a Tensor9 control plane in your new AWS account (this takes several minutes to complete):
  1. Create a new Tensor9 app.
Note: The length of the displayName field must be 32 characters or fewer.

Publish your TF and bind it to your new app

Tensor9 works by compiling your TF for each appliance your want to deploy to. So, your next step is to publish your TF to your Tensor9 control plane:
This will return a native stack id, which will will look something like this: s3://t9-ctrl-000001/your-stack.tf.tgz The next step is to bind your published stack to your app:
This registers your stack with your app so that you can release your app/stack combination to appliances. In the future, you can publish new versions of your stack (using the tensor9 stack publish command) without having to bind the app again.

Create a test appliance and test your app

  1. Create a test appliance:
  1. View the output of tensor9 report to determine when your test appliance is ready for a release. While the test appliance is creating, tensor9 report displays output such as:
When the appliance is ready, tensor9 report displays output such as:
  1. Create a release to your test appliance:
After a few minutes, the workspace bundle for your TF root module downloads into a new directory that is named after your appliance.
  1. Change into the new directory that contains the deployment stack for your test appliance:
  1. Deploy as normal by running tofu init followed by tofu apply.
  2. Run tofu show to review the resulting created resources.

Release an infrastructure change

You can release infrastructure changes to your stack at any time.
  1. Update your origin stack with any desired change. For example, you could enable versioning on the AWS S3 bucket that was created when initially publishing your origin stack.
Important: The next step will overwrite the previous origin stack. All new releases will come from the most recently published version of your origin stack.
  1. Re-publish the origin stack to Tensor9:
If the origin stack is published successfully, the following message is displayed:
Your native stack id is displayed. You will need this stack id in the next step.
  1. Create a new release:
After a few minutes, the workspace bundle for your TF stack downloads into a new directory that is named after your app.
  1. Change into the new directory that contains the deployment stack for your test appliance:
  1. Deploy as normal by running tofu init followed by tofu apply.
  2. Run tofu show to review the resulting created resources.