Cloud Setup

PX runs your jobs in your own cloud account. So before px cluster up can spin anything up, it needs credentials it's allowed to use. You log in with your cloud's own CLI, and PX picks up the credentials from there.

Supported providers

During the private beta, PX runs on GCP and AWS. Azure and DigitalOcean are coming soon.

Authenticate

Pick your cloud and run its login flow. You'll need its CLI/SDK installed first: gcloud for GCP, or the aws CLI for AWS.

GCP

gcloud auth application-default login

AWS

# Long-lived access keys:
aws configure

# Or, if your org uses AWS SSO / IAM Identity Center:
aws sso login --profile <your-profile>

On GCP, point PX at a project: gcloud config set project <PROJECT_ID> (list them with gcloud projects list).

On AWS, if you keep more than one profile (common with SSO), point PX at the right one: export AWS_PROFILE=<your-profile>.

Where are credentials stored?

Your credentials are stored in the standard location used by your cloud's CLI: AWS in ~/.aws/, GCP in ~/.config/gcloud/. PX uses these credentials to provision and manage cloud resources on your behalf.

Verify

One command tells you whether PX can reach your cloud:

px doctor cloud

When a provider is good to go, its line shows enabled:

✓ aws  enabled
✓ gcp  enabled

If something's off, the line shows disabled with the reason, and in most cases the exact command to fix it:

○ aws  disabled (SSO session expired or missing)
       $ aws sso login --profile development
       For more info: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html
○ gcp  disabled (credentials expired)
       $ gcloud auth application-default login
       For more info: https://cloud.google.com/docs/authentication/provide-credentials-adc

px doctor cloud only diagnoses issues. It doesn't try to log you in. It is up to you to configure your cloud CLI and log into your cloud account(s).

Restricted or org-managed accounts

The steps above cover a normal account where you can grant yourself access. If you're on a locked-down account (custom IAM roles, minimum-privilege policies, an admin who controls permissions, etc), you'll need the exact cloud permissions the provisioner requires.

PX provisions VMs with SkyPilot under the hood today, so their permissions guides are the source of truth for that:

• GCP permissions
• AWS permissions

Once px doctor cloud shows enabled for your cloud, you're ready to bring up a cluster. Head back to the Quick Start to generate a spec and run px cluster up.