Valet Dedicated
Each Valet Dedicated release: what it adds to your installation and how to upgrade.
The upgrade guide covers each step in full.
Install into subnets another account shares with you.
Before you upgrade
ec2:CreateVpc, ec2:DeleteVpc, and ec2:ModifyVpcAttribute.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.
Let approved apps reach systems in your own network.
Before you upgrade
upgrade refuses every earlier release, so ask Valet before you plan a move to it.Private systems. Let an app reach a system in your network, such as a database, once an Admin approves it in the dashboard.
16x sizes. Run processes and Valet PostgreSQL at economy-16x and standard-16x.
Firewall list. releases egress prints the hosts a release reaches for the options you choose.
Rotate an app's service token with valet apps token rotate, without an outage.
Every destroy command asks you to confirm, or takes --yes.
A crashed Node app now shows the error it threw.
A small follow-up to 0.9.0 that corrects the operator guide.
Every link in the operator guide now opens a page you can reach.
The scheduled-agent starter no longer gives the agent the same name as its cron channel.
Verify every release, preview each upgrade, and send telemetry to your own collector.
Before you upgrade
terraform apply before upgrade. The deployment role gains read access to the release signature.pending-reboot until the next reboot; nothing breaks meanwhile.upgrade 0.9.0 --plan first. Upgrade refuses a release that does not list your version as a predecessor; ask Valet if refused.Signed releases. releases fetch and upgrade verify the manifest's signature and copy images by the digests it names.
Safer upgrades. upgrade --plan shows every change first. Upgrades take a lock and snapshot the database before a migration.
Telemetry to your collector. Export metrics and traces over OTLP to Datadog or any OpenTelemetry collector.
Amazon Bedrock. Run Claude models through Bedrock in your own account, signed with each task's IAM role.
Operator commands. releases list, roll, services suspend and resume, oauth-clients set, and access-rules.
Outbound endpoints. Each release ships egress.json, every host the installation contacts, so you can write firewall rules.
Least-privilege IAM. The module ships an IAM policy for the role that runs Terraform, and the database logs every connection.
Admins decide who may add custom connectors, and you can forbid public or password access installation-wide.
Run the installation from one tool, give apps PostgreSQL, and audit every write.
Before you upgrade
app_database = { enabled = true } and apply.VALET_DEDICATED_OPENAI_API_KEY before you run upgrade.Day-two commands. status, settings, users, orgs caps, policies, and support bundle, each with --output json.
App database. Turn on a private PostgreSQL instance that apps get databases from, backed up with the rest.
Audit log. Every allowed or refused write goes to a CloudWatch audit group. Read it with audit list or forward it.
Alarms and access logs. Send alarms to your SNS topic, set log retention, and write load balancer access logs to your bucket.
Private destinations and gateways. Let connectors reach listed hosts in your network, and route model calls through your own gateway.
OpenAI models. Add an OpenAI key to offer OpenAI models beside Claude.
Each release carries its catalog, so the installation never downloads connectors or skills from Valet.
People enter secrets on a dashboard page, and scripts call private apps with service tokens.
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.VALET_DEDICATED_ANTHROPIC_API_KEY and VALET_DEDICATED_WORKOS_API_KEY, or upgrade prompts for them.Backups. AWS Backup copies the database and file system every day and keeps them 35 days.
Keys at the first upgrade. upgrade collects the Anthropic and WorkOS keys before it starts any service.
Company-sized defaults. A warm standby pool, caps of 500 agents and apps, and a secrets release policy in every new organization.
Only an administrator creates organizations, and channels that need inbound internet stay hidden.
The dashboard shows your installation's MCP address and your support contact.
The installation refuses impersonated sessions. No one outside your company can sign in as your people.
One fix for upgrades run right after an apply.
upgrade run seconds after terraform apply no longer fails with a 403 while IAM changes propagate.
The install and upgrade pages work for every release, not one version.
Install and upgrade commands take the release from one variable, so you copy them as written.
The same installation as 0.3.0, published again with no change you need to act on.
No change to the module or the operator tool. You can skip this release.
Fetch a verified release and install it with the operator guide.
Release bundles. Each release holds the Terraform module, the valet-dedicated tool, a manifest, and its notes.
Verified fetch. releases fetch checks every file against the manifest and writes nothing if one fails.
Operator guide. Prepare, install, and upgrade pages ship inside the module, matched to your release.
The Terraform module takes the layout every later release builds on.
Before you upgrade
Data and installation modules. Keep the database, buckets, and file system in their own state, apart from everything else.
Two clusters. Platform services run apart from the runtimes and builders that run your people's code.
Examples. Single-state, split-state, and Terragrunt roots to start from.
The whole Valet platform, run in your account and reachable only inside your network.
Valet Dedicated. Your people build and run agents, sites, and apps in your AWS account. Your data stays there.
Private by design. An internal load balancer serves the installation's hosts only inside your VPC.
Your identity provider. People sign in through your identity provider, connected through WorkOS.
Operator tool. valet-dedicated upgrade deploys a release, check verifies it, and settings set and users set-role manage it.