# Separate BYOC Region and Cluster Lifecycles

`cp9 byoc activate` makes the session's BYOC regional control plane and customer-account contract ready but does not create a customer TiDB dataplane or TiDB cluster. A separate product proof enters the real first-cluster path, which may create the DataPlane VPC/EKS before it creates, reaches, deletes, and proves absence of the TiDB cluster; normal `cp9 destroy` then tears down any retained dataplane and the session substrate. This matches the executable `auto-deploy/terraform/aws/byoc` boundary, keeps product sizing choices out of activation, and avoids hiding product mutations inside an infrastructure command.