# Run Production Account Setup Without an O11Y Runtime

CP9 uses `byoc.account_setup.profile` to run the official AWS customer
account-setup contract unchanged in the exclusive customer account. The setup
requires both TiDB and O11Y hosted-zone IDs and deploys the fixed
`tidbcloud-byoc-setup-deploy`, `tidbcloud-byoc-setup-dataplane`, and
`tidbcloud-byoc-setup-o11y` CloudFormation stacks. CP9 does not fork their IAM
role names, trust policies, or permission semantics. This supersedes the
session-scoped bootstrap equivalent in ADR 0025.

The first implementation slice still excludes the O11Y runtime. Account-setup
roles and an O11Y hosted-zone prerequisite do not make O11Y ready: CP9 does not
create the customer O11Y shoot VPC/EKS, deploy O11Y or ACS services, configure
O11Y peering, or run metrics/logging/alerts acceptance. Status reports the O11Y
runtime as explicitly not deployed. This boundary preserves the real customer
setup path while keeping runtime scope focused on the BYOC cluster core
lifecycle.