Skip to content
StratumStratum Docs

Describe an availability zone.

GET
/v1/regions/{regionName}/availability-zones/{azName}
Code sample: Shell / cURL
curl --request GET \
  --url https://stratum.example.com/v1/regions/example/availability-zones/example \
  --header 'Authorization: Bearer <token>'

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
regionName
required
string
/^[a-z][a-z0-9]+(-[a-z0-9]+)*$/
azName
required
string
/^[a-z][a-z0-9-]+[a-z]$/

Responses

Section titled “Responses”

200

Section titled “200”

The AZ.

Media typeapplication/json
object
name
required
string
/^[a-z][a-z0-9-]+[a-z]$/
region
required
string
/^[a-z][a-z0-9]+(-[a-z0-9]+)*$/
displayName
required
string
description
string
state
required

active accepts new resources. draining is an operator’s maintenance state: no new resources, existing ones continue. unavailable means no node that can run workloads is in this zone any more — derived from the nodes by the control plane, never set by hand, and back to active as soon as a node claims the zone again; do not place new resources here. deleted is terminal.

string
Allowed values: active draining unavailable deleted
createdAt
required
string format: date-time
updatedAt
required
string format: date-time

Example 

{
  "state": "active"
}

404

Section titled “404”

Resource not found.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example 

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}