Create a new data plane
Creates a new data plane object. Persists the rendered data plane spec, and returns 202 with the data plane in status=requested. Requires BYOC enabled org and org admin. The cloud of the control plane selects the AWS, the Azure, or the GCP request. For AWS, the control plane uses the organization’s assigned external ID to assume the AWS role. Configure that ID in the role’s trust policy before creating a data plane. For Azure, the control plane uses the Entra tenant and the resource group in the request. For GCP, the control plane impersonates the provisioner service account in the request. That service account must be in the request’s project, and its description must be the organization’s assigned external ID.
Authorizations
Body
- Option 1
- Option 2
- Option 3
40Use customer-managed IAM roles created by the LangSmith BYOIAM Terraform module.
Use a public EKS API endpoint restricted to LangSmith control-plane egress IPs instead of creating a managed PrivateLink endpoint service. Defaults to false.
TraceStorage selects the run and trace store. Defaults to CLICKHOUSE.
CLICKHOUSE, SMITHDB VPCCIDR is used only when LangSmith creates the VPC.
Response
Data plane requested
requested, provisioning, provisioning_failed, active, updating, inactive, deprovisioning, deleted, revoked 
