Diagnostics

SKE has no single doctor command. A cloud provider connection is checked from the dashboard, and a deployment from the CLI.

Checking a cloud provider

Go to Connections, Cloud providers and open the provider’s actions menu:

Action	What it checks
Diagnostics	The provider’s credentials are valid, and its container registry (ECR on AWS, Artifact Registry on GCP) is reachable
Re-validate	The IAM role or service account has the permissions each feature group needs (see the IAM Reference)

Run both after changing your IAM role or GCP service account.

Troubleshooting a deployment

If ske deploy fails, the CLI prints the error and the last lines of the build or deployment output. To look further:

# The latest deployment and its output
ske status --env production

# Any deployment, by ID, with its full output log
ske deploy show 7246183051948032011

# The application's logs around the failure
ske logs production --since 30m --level error

Common causes:

• Expired or invalid cloud provider credentials (run Diagnostics)
• Missing IAM permissions for a feature the environment uses (run Re-validate)
• A database, cache or network that is still provisioning or failed (ske job list, ske job show <job-id>)
• Docker not running locally

In CI

ske exits with a code that says what failed, so a pipeline can tell them apart:

Code	Meaning
0	Success
1	General failure
2	Usage error (bad flags or arguments)
3	Authentication error
4	API error
5	Conflict

--json prints machine-readable output for any command.