INFO 2004 Chap.4 The AWS Well-Architected Framework
The AWS Well-Architected Framework
The Well-Architected Framework is taught here as a review instrument built around five pillars: operational excellence, security, reliability, performance efficiency and cost optimisation. The course lists 27 design principles across those pillars: five, seven, five, five and five respectively. Preserve that exact version.
The chapter's purpose is not merely to memorise labels but to convert each principle into a review question and improvement action. Reviews should be constant and consistent, blame-free, lightweight—hours rather than days—and conducted as conversations rather than audits.
That stance matters for Assignment 2.2 because a prototype justification becomes stronger when it shows how the architecture was challenged, what issue was discovered and what action follows. Cross-vendor material can broaden the comparison, but the licensed comparison table is not reproduced.
What this chapter covers
- 01
Framework review as a conversation, not an audit
- 02
Operational excellence and its five principles
- 03
Security and its seven principles
- 04
Reliability and its five principles
- 05
Performance efficiency and its five principles
- 06
Cost optimisation and its five principles
- 07
Turning all 27 principles into actions
Run a five-pillar review on a growing customer workload
- 1Operational excellence: ask how changes are made, reversed and learned from; record one process action.
- 1Security: ask how identity, traceability, layered protection and event preparation are evidenced; record one control action.
- 1Reliability: ask how failure recovery, recovery testing, horizontal scaling, capacity and automated change are handled.
- 1Performance efficiency: ask how the chosen resources meet requirements as demand and technology change.
- 1Cost optimisation: ask how consumption, efficiency and expenditure attribution connect to business value.
Key terms
- Operational excellence
- Supporting development and running workloads effectively while learning and improving procedures.
- Security
- Protecting data, systems and assets while using cloud technologies to improve security.
- Reliability
- A workload performing its intended function correctly and consistently across its lifecycle.
- Performance efficiency
- Using computing resources efficiently to meet requirements as demand and technology change.
- Cost optimisation
- Delivering business value at the lowest price point through deliberate consumption and expenditure management.
- Architecture review
- A lightweight, blame-free conversation that identifies critical issues and improvement actions.
The AWS Well-Architected Framework FAQ
How many pillars are taught in INFO 2004?
Five: operational excellence, security, reliability, performance efficiency and cost optimisation.
How many design principles are listed?
Twenty-seven in total: five, seven, five, five and five across the pillars in that order.
Is a review an audit?
No. The course says reviews should be conversations rather than audits and should take hours, not days.
Why does the framework matter for Assignment 2.2?
It supplies a structured way to justify a prototype and turn architectural concerns into improvement actions.
Assessment move
Build five recall cards, one per pillar, then add the exact design principles under each. Revise with a scenario: turn every principle into a question, mark what evidence you would seek, and write one improvement action. Keep the five-pillar version fixed even if outside material presents a newer public version; this guide follows the course materials taught here.
Working through The AWS Well-Architected Framework in INFO 2004? Sia is AskSia’s AI Computer Science tutor — ask any INFO 2004 The AWS Well-Architected Framework question and get a clear, step-by-step explanation grounded in how INFO 2004 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
