INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: Applied container, data, cost and AI labs

Exercise ECS deployment health|Startup, ALB and the new revision

Distinguish task startup, ALB health and the required count of the new revision.

What you will learn

Identify the next runtime evidence after a GitHub Actions deployment.

Prerequisite

The cases use fictional inputs.

Start the exercise →

What to predict

Distinguish task startup, ALB health and the required count of the new revision.

From conditions to the decision
From conditions to the decision1: New revision task — Align conditions — ALB health outcome. 2: ALB health outcome — Compare outcomes — Required new revision count reached. 3: Required new revision count reached — Verify the decision — Decision123New revision taskALB health outcomeRequired newrevision countreachedDecisionFrom conditions to the decision1: New revision task — Align conditions — ALB health outcome. 2: ALB health outcome — Compare outcomes — Required new revision count reached. 3: Required new revision count reached — Verify the decision — Decision123New revisiontaskALB healthoutcomeRequired newrevision countreachedDecision
  1. New revision task → ALB health outcomeAlign conditions
  2. ALB health outcome → Required new revision count reachedCompare outcomes
  3. Required new revision count reached → DecisionVerify the decision
New revision task
Running / Stopped during startup
ALB health outcome
200 / 503
Required new revision count reached
Yes / No
Decision
Identify the next runtime evidence after a GitHub Actions deployment.

Compare the cases

Synthetic observations
CaseConditionsDecision
Trial 1New revision task Running, ALB health outcome 200, Required new revision count reached YesThe modeled conditions pass. Exercise a representative client request.
Trial 2New revision task Stopped during startup, ALB health outcome 200, Required new revision count reached YesStartup: reconcile the stop reason and revision.
Trial 3New revision task Running, ALB health outcome 503, Required new revision count reached YesApplication readiness: inspect the dependency behind the 503.
Trial 4New revision task Running, ALB health outcome Timeout, Required new revision count reached YesReachability: inspect the target port and path.
Trial 5New revision task Running, ALB health outcome 200, Required new revision count reached NoDeployment incomplete. Verify the revision count and client behavior.

Acceptance and limits

The task and target are synthetic. The exercise changes no deployment.

Read the initial conditions and operational goal.

Change one condition and compare the decision.

Record the model boundary and outstanding checks.

Change a condition

The task and target are synthetic. The exercise changes no deployment.

The modeled conditions pass. Exercise a representative client request.

Check your understanding

Choose an option to see the result and explanation.

What happens in trial 1?
Read the answer and reason

Answer: The modeled conditions pass. Exercise a representative client request. · New revision task Running, ALB health outcome 200, Required new revision count reached Yes → The modeled conditions pass. Exercise a representative client request.

What happens in trial 2?
Read the answer and reason

Answer: Startup: reconcile the stop reason and revision. · New revision task Stopped during startup, ALB health outcome 200, Required new revision count reached Yes → Startup: reconcile the stop reason and revision.

What happens in trial 3?
Read the answer and reason

Answer: Application readiness: inspect the dependency behind the 503. · New revision task Running, ALB health outcome 503, Required new revision count reached Yes → Application readiness: inspect the dependency behind the 503.

Check, then explain in your own words

  1. Read the initial conditions and operational goal.
  2. Change one condition and compare the decision.
  3. Record the model boundary and outstanding checks.
Check your understanding: Identify the next runtime evidence after a GitHub Actions deployment.

The task and target are synthetic. The exercise changes no deployment.

Record the model boundary and outstanding checks.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.