Sustainability

The pillar as an engineering definition, the efficiency levers, and sustainability as a stated trade-off

Provision less, use more of itAWS's own two-part definition
Track ratios, not totalswork per resource survives growth
Storage grows without a decisionlifecycle automation, not review
One pillar among sixwrite the trade-off down

1.Sustainability as an Architectural Concern

Sustainability is one of the six Well-Architected pillars, and AWS defines it in engineering terms: continually improving sustainability impacts by reducing energy consumption and increasing efficiency across all components of a workload — maximizing the benefit from provisioned resources and minimizing the total resources required. That is a statement about architecture, not about reporting.

Key features

AWS defines sustainability as the ability to continually improve sustainability impacts by reducing energy consumption and increasing efficiency across all components of a workload
The definition names two levers explicitly: maximizing the benefits from provisioned resources, and minimizing the total resources required
Under the shared responsibility model, the efficiency of the data centre is AWS's concern and the efficiency of the workload is yours
The pillar was added to what was previously five pillars, so older Well-Architected material and older reviews will not include it
Almost every sustainability action also reduces cost, because both are functions of resources provisioned and resources used
The unit that matters is work per resource — requests served per provisioned vCPU-hour — rather than absolute usage, which grows with a healthy business

The two levers in the definition, made concrete

The two levers in the definition, made concrete
Lever	Means	Examples
Maximize benefit from what is provisioned	Raise utilization	Bin-pack containers, consolidate under-used instances, scale in aggressively
Minimize total resources required	Do less work	Cache, CDN, efficient queries, smaller payloads, delete unused data
Both, at once	Right-size and schedule	Match capacity to demand rather than to peak

Signature

sustainability = maximize benefit from provisioned resources + minimize total resources required

AWS defines sustainability as reducing energy consumption and increasing efficiency across a workload — maximize the benefit from what you provision, and minimize what you provision. Track it as a ratio (work per resource), and ask the question in design review, not in a report.

2.Efficiency Levers That Reduce Impact

The levers are the ones you already know from cost work, read with a different question. High utilization means fewer machines doing the same work. Right-sizing means not provisioning capacity that is never used. Lifecycle policies mean cold data stops occupying expensive, always-spinning storage. And architecture decides how much work has to happen at all.

Key features

Utilization is the dominant lever: a fleet at 15% utilization is provisioning roughly six times the resources its work requires
Right-sizing addresses the same gap from the other side, matching instance size to observed demand rather than to a guess
Storage lifecycle policies move data to colder classes and delete what has expired, so bytes nobody reads stop occupying the fastest tier
Deleting unused data is the most complete form of efficiency — untouched snapshots, orphaned volumes, and superseded backups are pure overhead
Managed and serverless services generally raise utilization because the provider pools capacity across customers rather than leaving yours idle
Reducing data transferred — smaller payloads, compression, a CDN closer to users — cuts both network resources and origin compute

Levers, and the measurement that shows whether they worked

Levers, and the measurement that shows whether they worked
Lever	Action	Measure
Compute utilization	Bin-pack, consolidate, scale in faster	Average utilization across the fleet
Right-sizing	Match size to observed demand	Provisioned vs used, per resource
Scheduling	Stop non-production out of hours	Instance-hours per week
Storage lifecycle	Tier and expire automatically	GB by storage class, and age of the oldest data
Data deletion	Remove orphaned volumes, snapshots, logs	GB stored that nothing references
Payload efficiency	Compression, smaller responses, CDN	GB transferred per request

Where the resources actually go

Provisioned

what you pay for and power

Utilized

the fraction actually doing work

Useful work

requests served, bytes delivered

Stored

and how much of it is ever read

Command

text

# S3 lifecycle: tier and expire without anyone remembering to
Days 0-30    Standard          (actively read)
Days 31-90   Standard-IA       (occasionally read)
Days 91-365  Glacier Flexible  (rarely read)
Day 366      Expire            (unless retention says otherwise)

Utilization first (a fleet at 15% provisions six times what it needs), then right-sizing and scheduling, then storage lifecycle and deleting what nothing reads, then payload and transfer efficiency. Nearly all of it reduces cost by the same mechanism.

3.Sustainability as a Trade-off Among the Pillars

The Well-Architected Framework has six pillars, and AWS says explicitly that you make trade-offs between them based on business context. A development environment might be optimized for sustainability and cost at the expense of reliability; a mission-critical system optimized for reliability at the expense of both. Sustainability is one voice in that decision, not an override.

Key features

AWS states you make trade-offs between pillars based on business context, and that these business decisions can drive engineering priorities
AWS gives the example of optimizing for sustainability and cost at the expense of reliability in development environments
AWS also gives the opposite: optimizing reliability with increased cost and sustainability impact for mission-critical solutions
AWS notes that security and operational excellence are generally not traded off against the other pillars
Sustainability and cost usually move together, so the genuine tensions are with reliability (redundancy) and performance (headroom)
The trade-off is per workload: the same organisation can reasonably hold different positions for a payments ledger and an internal report

Where sustainability genuinely trades against another pillar

Where sustainability genuinely trades against another pillar
Decision	Gains	Costs in sustainability
Multi-Region hot standby	Near-zero RTO	A full duplicate environment, mostly idle
Provisioned concurrency	No cold starts	Environments held ready whether used or not
Over-provisioned headroom	Absorbs spikes without scaling delay	Capacity idle most of the time
Multi-AZ everything	Survives an AZ failure	Standby capacity that serves no traffic
Longer retention	More recovery points, more audit history	Storage for data almost never read

Command

text

# The six pillars
operational excellence · security · reliability
performance efficiency · cost optimization · sustainability
# Security and operational excellence are generally not traded away.

Six pillars, traded against each other per workload and per business context. Sustainability and cost usually agree; the real tensions are with reliability and performance headroom. Write the trade down — an unstated trade-off is an oversight, and security and operational excellence are generally not traded away.

Spotted a mistake on this page? Tell us.

Read Sheet