Describe a lifecycle hook.
curl --request GET \ --url https://stratum.example.com/v1/projects/example/asg/groups/example/hooks/example \ --header 'Authorization: Bearer <token>'Cedar-gated on asg:DescribeAutoScalingGroup.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”The hook.
A lifecycle hook: a pause on a transition plus an API.
A launching hook holds a new instance at Pending:Wait once it is running;
a terminating hook holds an instance at Terminating:Wait (deregistered
from its target groups, the drain running alongside). Whoever the tenant
already runs — the instance agent, a user-data script, their CI — answers
with CompleteLifecycleAction, or extends the wait with a heartbeat; a
hook nobody answers times out to defaultResult. No auto-fire at 2.0.
object
lh-…; stable across replacements of the same name.
Applied when the hook times out. On a launching hook ABANDON
terminates the instance and the group launches a replacement; on a
terminating hook it terminates at once without waiting for the drain.
The wait, restarted by every heartbeat (30–7200, default 3600).
Free-form JSON handed to the caller (surfaced on the instance’s hook state; the platform does not interpret it).
Example
{ "transition": "autoscaling:EC2_INSTANCE_LAUNCHING", "defaultResult": "CONTINUE"}Authenticated but not authorized.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
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.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
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
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Resource not found.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
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.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
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
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}