Skip to main content
This guide creates your Tensor9 BYOC control plane in a dedicated AWS account you own.

Prerequisites

  • A Tensor9 API key and the CLI: Follow Get a Tensor9 API key.
  • A dedicated AWS account: Use it only for Tensor9 BYOC. Control planes run in the AWS us-west-2 (US West, Oregon) region.
  • AWS credentials for that account with administrator permissions, for example through the AWS CLI.

Set up your Tensor9 BYOC control plane

Your Tensor9 BYOC control plane is the engine that manages your customer appliances. It consists of a set of resources that are provisioned directly into your own dedicated Tensor9 BYOC AWS account. Your control plane is responsible for:
  • Managing your origin stacks.
  • Creating and managing appliances.
  • Performing deployments to appliances.
  • Synchronizing telemetry from appliances back to your observability sink.
  • Creating operations endpoints so that you can remotely operate appliances.
Add -awsProfile <name> to use a different AWS CLI profile, or -region us-west-2 if your AWS configuration defaults to another region. Setup takes about 10 minutes and writes its logs to logs/tensor9-vendor-setup.log. It may save the SSH private key for your controller machine in the current directory; keep that file private. If your environment is AWS, setup automatically provisions a PrivateLink endpoint service that makes AWS PrivateLink available as a network path for the appliance-to-control-plane channel. Pass -noAwsPrivateLinkRdv on the setup command to suppress the endpoint service, which removes PrivateLink as a network-path option for your form factors.

Your controller profile

Setup enrolls this machine and writes a controller profile, such as root-prod1-<your-vendor>, to ~/.tensor9/config.json as your default. Later commands, such as app create, use it with no API key or profile options.

Verify your control plane

Run tensor9 report for a summary of your control plane, including its health status.
For a newly created control plane with no apps or appliances yet, the output will look like this:
This confirms your control plane is running and ready to use. You can now proceed to create your first app and begin deploying to customer appliances.

Next steps

Now that your control plane is installed and running, explore these topics to start using Tensor9 BYOC: