A Platform is a connection to an external execution service that hosts
the pipelines, notebooks, or functions Polysync orchestrates. Each Platform
record stores the provider type, authentication method, and the attribute
values needed to call that provider's APIs.
Common workflow
- Create a Secret Vault if your chosen authentication method needs stored
credentials (skip this for Managed Identity, Polysync SP, Role ARN, or
Workload Identity Federation).
- Create the Platform — pick the provider, the authentication method, and
fill in all required attributes.
- Test connectivity to make sure Polysync can reach the platform with
the provided credentials.
- Import platform pipelines as Jobs (or define Jobs manually).
- Optionally link a Contention Profile to cap concurrency / rate against
the platform.
Authentication trade-offs (general)
- Prefer credential-free options whenever the platform supports them:
Polysync Service Principal (Azure Marketplace tenants), Managed Identity
(Polysync hosted on Azure), Workload Identity Federation (cross-cloud GCP),
Role ARN AssumeRole (AWS).
- Service Principal / Access Key options work everywhere but require secret
rotation — store the secret in a Vault, never inline.
- Default Credential / Default Credentials chains are fine for dev/test but
are hard to audit in production because the resolved identity depends on
the host environment.
Listing and importing pipelines
Once a Platform is connected, the editor's Get Pipelines action lists the
pipelines on that platform. You can then import all of them or just a subset
as Jobs in one step. The AI Copilot exposes the same flow via the
list_platform_pipelines and import_platform_jobs tools.