Private Alien Instances
Private managers are now called Private Alien Instances. A Private Alien Instance runs the Alien manager in your own AWS, Google Cloud, or Azure account, so your customers' deployment traffic stays in your cloud.
More of that traffic now stays there, and never reaches Alien's hosted API:
- Logs: log bodies no longer pass through Alien's hosted API.
- Commands: the parameters and results of commands and Remote Operator operations stay in the instance.
- Values: with a values key, secret inputs, environment variables, and dynamic container secrets are sealed with a key in your account. Alien keeps only metadata, such as the name and when it changed. The dashboard and CLI send each value straight to the instance.
Settings → Private Alien Instances lists every instance in the workspace with its cloud, region, status, and how many deployments it manages. For each project, choose which instance receives new deployments on each platform. Existing deployments keep their instance. Each deployment's page shows which instance manages it.
- Values key: an instance set up before the key existed needs its initial setup to run again with
InputValuesKeyset totrue. Values set before then stay with Alien - Older CLIs: an instance with a values key refuses values from a CLI that sends them to Alien. Run
alien upgrade - Plan: Private Alien Instances need the Pro plan