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: AWS design through six pillars

AWS Well-Architected explained: design trade-offs across six pillars

AWS Well-Architected is a framework for reviewing how you design and operate a system through six pillars. Adding an application instance, restricting access or reusing a result can bring benefits and new constraints. Follow one report application and separate the intended improvement, the trade-offs and the evidence still needed.

What you will learn

Turn the six pillars into practical design questions. Explain a change’s benefits, trade-offs and evidence needs, distinguishing a violated requirement from an outcome that remains unverified.

Prerequisite

For readers beginning to think of AWS as a combination of services. An application processes user requests; a workload includes the application, data and operations that serve a purpose. The example is explained here. No AWS account or hands-on operation is required.

Start with one report application and a shared set of requirements

A pillar is a design perspective, not a service category or a step in an execution sequence. Use AWS Well-Architected to discuss the advantages and disadvantages of decisions and identify improvements. Checking six boxes does not certify a system as secure.

One application and dataset, reviewed later through six perspectives
One application and dataset, reviewed later through six perspectives1: Reader — Request a report — Report app. 2: Report app — Retrieve the required content — Saved reports12ReaderReport appSaved reportsOne application and dataset, reviewed later through six perspectives1: Reader — Request a report — Report app. 2: Report app — Retrieve the required content — Saved reports12ReaderReport appSaved reports
  1. Reader → Report appRequest a report
  2. Report app → Saved reportsRetrieve the required content
Reader
An authorized staff member reads the required morning report.
Report app
Checks the reader, selects the permitted report and returns its contents.
Saved reports
Contains prepared results and source records that must be retained.

The lines show request and data relationships. They do not depict a real network path, an AWS deployment or the complete authentication process. Keep the application’s purpose and required data fixed when comparing later changes.

Business requirements stipulated for this example
RequirementWhat is given
Who can readOnly authorized staff may read the reports they need.
Required freshnessThe morning report must include approved changes through 07:00.
Data retentionKeep source records for 30 days. Recreating a prepared report is separate from retaining its source.
Failure preparationDecide what must be recovered and how to check report reads if the application becomes unavailable. No recovery-time limit is specified here.
Comparison limitsPrices, response times and emissions have not been measured. Actual improvement from a deployment change is unverified.

Translate the six pillars into practical questions

The six pillars are operational excellence, security, reliability, performance efficiency, cost optimization and sustainability. A change can affect several pillars; they do not describe six separate systems to build.

Six questions about the same report application
PillarFocusQuestion for this application
Operational excellenceImprove change, observation and response to keep delivering the required outcomes.Can we identify the changed version and owner, detect problems and improve the procedure?
SecurityProtect data, systems and assets.Who may read what? Does that role also need permission to change or delete it?
ReliabilityProvide the intended function correctly when it is needed.How will staff regain the required report if the app or a dependency fails?
Performance efficiencyMatch resources and approaches to performance requirements.Can the app return the required correct result quickly enough when demand is concentrated?
Cost optimizationExamine spending against the value the workload must deliver.Can we remove unnecessary usage while meeting read, freshness, retention and recovery requirements?
SustainabilityExamine resource use and environmental impact for the useful output.Are we recomputing the same result unnecessarily, or adding avoidable storage and transfer?

Operations and security: distinguish making a change from delegating permission

Operational excellence considers ownership, procedures, observations and learning from problems together. Make it possible to check the required report result, not merely that an automated job finished. Small reversible changes and continual refinement of procedures are part of this work.

Security concerns protecting the workload while allowing the right identities to perform the operations they need. Least privilege means limiting permission to the necessary scope. Access restrictions, action records, data protection and incident response are related controls, not interchangeable evidence.

Example: remove change and delete permissions from the reader role
Given condition or decisionWhat follows in this example
The report-serving role only needs to read specified reports.Changing and deleting reports are unnecessary permissions for that role.
A separate role is responsible for writing prepared reports.Review each role’s required operations rather than indiscriminately prohibiting all writes.
A permission change has been proposed but not applied to a real environment.It is a least-privilege proposal, not evidence of a safe rollout or successful real read.
Define post-change checks.Record the actor and change, then verify permitted reads and operations that should be rejected.

Choose an option to see the result and explanation.

Does an automated change’s completion record establish that operational checks are complete?
Read the answer and reason

Answer: Check the targeted change and the required read result too · Connect the changed version, target and operation result to the outcome users need.

Should a report reader role retain change and delete permissions it does not need?
Read the answer and reason

Answer: Consider removing those unnecessary permissions · This follows least privilege. Keep the writer role and post-change functional checks separate.

Reliability and performance: separate failure preparation from normal speed

Reliability considers whether the workload can provide its intended function correctly when expected. Test recovery procedures and examine shared dependencies. Having more application instances does not by itself guarantee the required data or continued use.

Performance efficiency considers how well technologies and resources meet the required work as demand changes. Compare the same correctness criteria, work and response-time requirements. Choosing a larger server or newer service does not establish the resulting performance.

Example: examine a proposal to run two application instances
CheckKnown and unresolved conditions
One application instance failsThe proposal provides another instance, but routing, transition, remaining capacity and data access have not been tested.
Both read the same storageAdditional app instances alone do not remove failure of a shared storage or identity dependency.
More readers arrive togetherCheck whether requests are distributed and correct results meet the response requirement under equivalent conditions. There are no measured results here.
Cost and operationsReview additional resources, rollout procedures, configuration consistency and ongoing cost too.

Choose an option to see the result and explanation.

Does the proposal for two app instances establish availability during a failure?
Read the answer and reason

Answer: No; check transitions, dependencies and required reads · Separate a deployment proposal from evidence that it provides the function during the relevant failure.

What should be aligned when comparing the performance of two proposals?
Read the answer and reason

Answer: Required results, data, workload and response criteria · Speed from different work or correctness criteria is not a direct comparison.

Cost and sustainability: preserve useful outcomes while reducing waste

Cost optimization relates expenditure to the value the business needs. Examine unnecessary usage and spending while maintaining required functionality, freshness, retention and recovery. A cheaper design that removes required outcomes is a different proposal. Estimates and actual bills are also different evidence.

Sustainability considers environmental impact and the compute, storage, transfer and other resources used for a useful outcome. Eliminating redundant work is a candidate improvement. Do not quantify energy or emissions reductions without examining the actual conditions.

Evaluate proposals against the original requirements
ProposalRequirement comparisonConclusion
Delete source records after 7 days instead of 30This violates the stipulated 30-day retention requirement.Do not adopt it under these requirements. This is a known conflict, separate from the unknown savings.
Reuse a report representing 06:00The report must include approved changes through 07:00, but this result is stipulated to omit later changes.The freshness requirement is not met, even if computation is avoided.
Reuse a 07:15 result stipulated to contain the required changes through 07:00The given freshness condition is satisfied. Reuse must still restrict who can read what.A candidate for reuse; access, recreation, performance, cost and environmental impact still need validation.

Choose an option to see the result and explanation.

Source records must be kept for 30 days. What about deleting them after 7 days to reduce cost?
Read the answer and reason

Answer: Reject it under these requirements · Reducing cost differs from optimizing cost while preserving required data retention.

Does a proposal to remove duplicate report generation establish reduced CO₂ emissions?
Read the answer and reason

Answer: No; it is a candidate whose impact still needs evaluation · Preserve the useful outcome and examine the resources and environmental impact.

Review one proposal through all six pillars

Now consider reusing the 07:15 result for the permitted readers. The input states that it includes the required changes through 07:00, so the stipulated freshness requirement is met. That does not approve the entire change.

Separate supplied evidence from the next checks
CategoryDecision record for this proposal
Established by the inputThe result is stipulated to include required changes through 07:00. Its 07:15 timestamp alone does not establish this.
Still unverifiedRecipient access, recovery, response time, cost and environmental impact. A written plan is not evidence it was carried out.
Next actionAssign owners and scope; check allowed/rejected reads, recreated contents, equivalent-load results, resource use and cost assumptions.

A trade-off exchanges a benefit for another burden or constraint. Reuse might avoid repeated work while adding freshness management, recipient access checks and storage operation. Do not add pillar scores to declare a winner. Record whether required conditions are met and who will decide whether remaining risks are acceptable.

Explain the decision and the evidence still needed

  1. Write down required functions, permitted readers, freshness, retention and failure conditions.
  2. Apply all six design questions to one proposed change.
  3. Distinguish a requirement conflict from a condition left unverified by missing evidence.
  4. Assign the checks and define which results would justify adoption or revision.

Choose an option to see the result and explanation.

The report must include changes through 07:00. A reused result omits everything after 06:00. What follows?
Read the answer and reason

Answer: Do not adopt it as-is; it fails freshness · The mismatch follows from the requirements and inputs without a price or performance measurement.

The 07:15 result meets freshness, but recipient access and recovery are untested. Which record is accurate?
Read the answer and reason

Answer: A freshness-qualified candidate; test access, recovery and other conditions before deciding · Separating established conditions from remaining checks makes the next actions concrete.

You can now explain the same application change through six design questions. Use related lessons later to deepen change management, access control, availability and performance. Do not change a real environment solely from the configuration labels in this example.

Check, then explain in your own words

  1. Express the six pillars as practical questions about the report application.
  2. Distinguish the 06:00 and 07:15 reuse proposals using the freshness requirement.
  3. Record benefits, burdens, established conditions and unresolved checks for one change.
Check your understanding: Someone reports that a report is now faster and cheaper to read. Is the six-pillar review complete?

No. Check the relevant requirements and evidence for content, permitted readers, retention, failure response, operations, environmental impact and other concerns.

Improvement in one perspective does not establish the other necessary conditions or make the remaining burdens acceptable.

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.