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.
Identify the next runtime evidence after a GitHub Actions deployment.
The cases use fictional inputs.
What to predict
Distinguish task startup, ALB health and the required count of the new revision.
- New revision task → ALB health outcomeAlign conditions
- ALB health outcome → Required new revision count reachedCompare outcomes
- 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
| Case | Conditions | Decision |
|---|---|---|
| Trial 1 | New revision task Running, ALB health outcome 200, Required new revision count reached Yes | The modeled conditions pass. Exercise a representative client request. |
| Trial 2 | New revision task Stopped during startup, ALB health outcome 200, Required new revision count reached Yes | Startup: reconcile the stop reason and revision. |
| Trial 3 | New revision task Running, ALB health outcome 503, Required new revision count reached Yes | Application readiness: inspect the dependency behind the 503. |
| Trial 4 | New revision task Running, ALB health outcome Timeout, Required new revision count reached Yes | Reachability: inspect the target port and path. |
| Trial 5 | New revision task Running, ALB health outcome 200, Required new revision count reached No | Deployment 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.
{"startup":"Startup: reconcile the stop reason and revision.","network":"Reachability: inspect the target port and path.","application":"Application readiness: inspect the dependency behind the 503.","waiting":"Deployment incomplete. Verify the revision count and client behavior.","ready":"The modeled conditions pass. Exercise a representative client request."}Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read the initial conditions and operational goal.
- Change one condition and compare the decision.
- 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.
Scope and conditionsDistinguish task startup, ALB health and the required count of the new revision.
Used in this lessonWhat to predict Acceptance and limits