Answer a few questions, then launch two CloudFormation stacks straight from this page — in your own AWS console, under your own account. Once you click Create stack, the install keeps running even if you close this tab; come back anytime to check progress.
We found an install in progress for tenant , saved in this browser.
BDB's own control plane runs in . Every AWS resource for this tenant is created in the region you pick below.
iam:PassRole on it.
BDB runs in private subnets with no public IPs. You need two existing private subnets in different Availability Zones, plus their route table ID(s).
Launches stack-discovery.yaml — a tiny stack that only calls read-only
ec2:Describe* APIs inside your own account and reports the result back to us. There is
no cross-account IAM role and nothing is ever assumed on our side. Safe to delete once you've picked
a VPC.
| Subnet | Zone | Range | Free IPs | Egress |
|---|
These control the EKS cluster and the BDB Helm charts installed on it.
Two stacks, launched one at a time. Once you click Create stack in the AWS console for either one, it keeps running in your account even if you close this tab.
Creates BDBCloudFormationExecRole, which the second stack runs as. Uses your own signed-in
console permissions — no service role needed for this one.
Creates the EKS cluster, node group, EFS and BDB's Helm charts — nested as one stack so the whole
thing runs unattended. On the CloudFormation review page, under Permissions, select
as this stack's IAM role before clicking Create stack —
that field can't be pre-filled by this link.
Tenant . Stack 2 runs unattended for about 45–60 minutes total — the checklist below updates itself as each stage finishes, or watch it live in your AWS CloudFormation console for full resource-level detail.
Couldn't load vendor.json from this site. It needs to be uploaded next to this
page — see tenant-launch-wizard/README.md.
Please use the link from your email to launch your BDB workspace. If you believe this is an error, contact support.