# Match the Auto-Deploy BYOC Region Boundary

`cp9 byoc activate` matches the executable `auto-deploy/terraform/aws/byoc` region boundary and therefore does not create a TiDB DataPlane CR, customer TiDB VPC, or dataplane EKS. The production Terraform root creates the seed regional control plane and the customer O11Y shoot; its shoot VPC/EKS is explicitly named and configured for O11Y, is passed to DPM as the O11Y VPC contract, and is not the TiDB dataplane. The workflow ends after Terraform apply and contains no `CreateDataPlane` or shared-pool call. CP9's first slice omits the O11Y shoot, so activation ends when `cp-byoc`, customer bootstrap/images, catalog, and cross-account configuration are ready. The later product cluster proof must enter cluster-ng's real first shared-pool/cluster workflow; that workflow calls the BYOC-configured DPM `CreateDataPlane` path to create the isolated customer VPC/EKS and PrivateLink before the first TiDB cluster becomes ready. The onboarding guide's Phase 3 wording groups broader platform automation and is not treated as the exact Terraform resource graph.