eks.clusters.list

List clusters

GET /eks/api/clustersIAM eks:ListClustersRead

Request syntax

GET /eks/api/clusters

Response

200 with the organization’s clusters by name (in the console’s current project only, when one is chosen), each as `get` describes it without the live parts: id, name, regionId, tier, version, kubernetesVersion, availableVersion, latestPatch, status, reconcileError, endpoint, endpointIpv4, allowedCidrs, endpointPublicAccess, endpointPrivateAccess, endpointPrivateIpv4, serviceAccountIssuer, vpcId, podCidr, serviceCidr, controlPlaneNodes, deletionProtection, autoscaler, logging, support, forcedUpgrade, slaPercent, createdAt, …. 403 without eks:ListClusters.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow eks:ListClusters on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud eks clusters list

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_eks_clusters_list.