Valet Dedicated

Changelog

Each Valet Dedicated release: what it adds to your installation and how to upgrade.

The upgrade guide covers each step in full.

v0.10.1

Shared VPC installs

Install into subnets another account shares with you.

Before you upgrade

  • 0.10.1 supports fresh installs only, like 0.10.0.
  • Turn on RAM sharing with AWS Organizations before you share the subnets.
  • If your Terraform role uses the module's IAM policy, update it. It gains ec2:CreateVpc, ec2:DeleteVpc, and ec2:ModifyVpcAttribute.
  • Fixed

    An install with vpc_owner_account_id set no longer fails at the first apply. The VPC owner runs the two commands the module prints.

v0.10.0

Private systems

Let approved apps reach systems in your own network.

Before you upgrade

  • 0.10.0 supports fresh installs only. upgrade refuses every earlier release, so ask Valet before you plan a move to it.
  • New

    Private systems. Let an app reach a system in your network, such as a database, once an Admin approves it in the dashboard.

  • New

    16x sizes. Run processes and Valet PostgreSQL at economy-16x and standard-16x.

  • Improved

    Firewall list. releases egress prints the hosts a release reaches for the options you choose.

  • Improved

    Rotate an app's service token with valet apps token rotate, without an outage.

  • Improved

    Every destroy command asks you to confirm, or takes --yes.

  • Fixed

    A crashed Node app now shows the error it threw.

v0.9.1

Guide fixes

A small follow-up to 0.9.0 that corrects the operator guide.

  • Fixed

    Every link in the operator guide now opens a page you can reach.

  • Fixed

    The scheduled-agent starter no longer gives the agent the same name as its cron channel.

v0.9.0

Signed releases and safer upgrades

Verify every release, preview each upgrade, and send telemetry to your own collector.

Before you upgrade

  • Run terraform apply before upgrade. The deployment role gains read access to the release signature.
  • The apply turns on IAM database authentication. The parameter group shows pending-reboot until the next reboot; nothing breaks meanwhile.
  • Preview with upgrade 0.9.0 --plan first. Upgrade refuses a release that does not list your version as a predecessor; ask Valet if refused.
  • New

    Signed releases. releases fetch and upgrade verify the manifest's signature and copy images by the digests it names.

  • New

    Safer upgrades. upgrade --plan shows every change first. Upgrades take a lock and snapshot the database before a migration.

  • New

    Telemetry to your collector. Export metrics and traces over OTLP to Datadog or any OpenTelemetry collector.

  • New

    Amazon Bedrock. Run Claude models through Bedrock in your own account, signed with each task's IAM role.

  • New

    Operator commands. releases list, roll, services suspend and resume, oauth-clients set, and access-rules.

  • Improved

    Outbound endpoints. Each release ships egress.json, every host the installation contacts, so you can write firewall rules.

  • Improved

    Least-privilege IAM. The module ships an IAM policy for the role that runs Terraform, and the database logs every connection.

  • Improved

    Admins decide who may add custom connectors, and you can forbid public or password access installation-wide.

v0.8.0

Day-two operations and app databases

Run the installation from one tool, give apps PostgreSQL, and audit every write.

Before you upgrade

  • If you apply the data and installation modules in separate states, apply the data module first.
  • To give apps a database, set app_database = { enabled = true } and apply.
  • To offer OpenAI models, set VALET_DEDICATED_OPENAI_API_KEY before you run upgrade.
  • New

    Day-two commands. status, settings, users, orgs caps, policies, and support bundle, each with --output json.

  • New

    App database. Turn on a private PostgreSQL instance that apps get databases from, backed up with the rest.

  • New

    Audit log. Every allowed or refused write goes to a CloudWatch audit group. Read it with audit list or forward it.

  • New

    Alarms and access logs. Send alarms to your SNS topic, set log retention, and write load balancer access logs to your bucket.

  • New

    Private destinations and gateways. Let connectors reach listed hosts in your network, and route model calls through your own gateway.

  • New

    OpenAI models. Add an OpenAI key to offer OpenAI models beside Claude.

  • Improved

    Each release carries its catalog, so the installation never downloads connectors or skills from Valet.

  • Improved

    People enter secrets on a dashboard page, and scripts call private apps with service tokens.

v0.7.0

Backups and safe defaults

Daily backups, company-sized defaults, and keys collected at the first upgrade.

Before you upgrade

  • terraform apply now creates an AWS Backup vault and a daily plan. Set backup.enabled = false to opt out.
  • Set VALET_DEDICATED_ANTHROPIC_API_KEY and VALET_DEDICATED_WORKOS_API_KEY, or upgrade prompts for them.
  • New

    Backups. AWS Backup copies the database and file system every day and keeps them 35 days.

  • New

    Keys at the first upgrade. upgrade collects the Anthropic and WorkOS keys before it starts any service.

  • Improved

    Company-sized defaults. A warm standby pool, caps of 500 agents and apps, and a secrets release policy in every new organization.

  • Improved

    Only an administrator creates organizations, and channels that need inbound internet stay hidden.

  • Improved

    The dashboard shows your installation's MCP address and your support contact.

  • Improved

    The installation refuses impersonated sessions. No one outside your company can sign in as your people.

v0.6.0

Upgrade reliability

One fix for upgrades run right after an apply.

  • Fixed

    upgrade run seconds after terraform apply no longer fails with a 403 while IAM changes propagate.

v0.5.0

Guide commands for any release

The install and upgrade pages work for every release, not one version.

  • Improved

    Install and upgrade commands take the release from one variable, so you copy them as written.

v0.4.0

Republished release

The same installation as 0.3.0, published again with no change you need to act on.

  • Fixed

    No change to the module or the operator tool. You can skip this release.

v0.3.0

Releases you install yourself

Fetch a verified release and install it with the operator guide.

  • New

    Release bundles. Each release holds the Terraform module, the valet-dedicated tool, a manifest, and its notes.

  • New

    Verified fetch. releases fetch checks every file against the manifest and writes nothing if one fails.

  • New

    Operator guide. Prepare, install, and upgrade pages ship inside the module, matched to your release.

v0.2.0

The settled module layout

The Terraform module takes the layout every later release builds on.

Before you upgrade

  • The module's resource addresses changed. Install 0.2.0 fresh; ask Valet before moving an 0.1.0 installation.
  • New

    Data and installation modules. Keep the database, buckets, and file system in their own state, apart from everything else.

  • New

    Two clusters. Platform services run apart from the runtimes and builders that run your people's code.

  • New

    Examples. Single-state, split-state, and Terragrunt roots to start from.

v0.1.0

Valet in your AWS account

The whole Valet platform, run in your account and reachable only inside your network.

  • New

    Valet Dedicated. Your people build and run agents, sites, and apps in your AWS account. Your data stays there.

  • New

    Private by design. An internal load balancer serves the installation's hosts only inside your VPC.

  • New

    Your identity provider. People sign in through your identity provider, connected through WorkOS.

  • New

    Operator tool. valet-dedicated upgrade deploys a release, check verifies it, and settings set and users set-role manage it.