Sustainability
Questions
6 best practices
- SUS02-BP01: BP01 - Scale workload infrastructure dynamically
- SUS02-BP02: BP02 - Align SLAs with sustainability goals
- SUS02-BP03: BP03 - Stop the creation and maintenance of unused assets
- SUS02-BP04: BP04 - Optimize geographic placement of workloads based on their networking requirements
- SUS02-BP05: BP05 - Optimize team member resources for activities performed
- SUS02-BP06: BP06 - Implement buffering or throttling to flatten the demand curve
5 best practices
- SUS03-BP01: BP01 - Optimize software and architecture for asynchronous and scheduled jobs
- SUS03-BP02: BP02 - Remove or refactor workload components with low or no use
- SUS03-BP03: BP03 - Optimize areas of code that consume the most time or resources
- SUS03-BP04: BP04 - Optimize impact on devices and equipment
- SUS03-BP05: BP05 - Use software patterns and architectures that best support data access and storage patterns
8 best practices
- SUS04-BP01: BP01 - Implement a data classification policy
- SUS04-BP02: BP02 - Use technologies that support data access and storage patterns
- SUS04-BP03: BP03 - Use policies to manage the lifecycle of your datasets
- SUS04-BP04: BP04 - Use elasticity and automation to expand block storage or file system
- SUS04-BP05: BP05 - Remove unneeded or redundant data
- SUS04-BP06: BP06 - Use shared file systems or storage to access common data
- SUS04-BP07: BP07 - Minimize data movement across networks
- SUS04-BP08: BP08 - Back up data only when difficult to recreate
5 best practices
- SUS06-BP01: BP01 - Communicate and cascade your sustainability goals
- SUS06-BP02: BP02 - Adopt methods that can rapidly introduce sustainability improvements
- SUS06-BP03: BP03 - Keep your workload up-to-date
- SUS06-BP04: BP04 - Increase utilization of build environments
- SUS06-BP05: BP05 - Use managed device farms for testing
The Sustainability pillar includes the ability to support development and run workloads effectively, gain insight into their operations, and to continuously improve supporting processes and procedures to deliver business value.
Key Areas
The Sustainability pillar includes the following key areas:
- Region Selection - Choosing Regions with lower carbon footprints
- User Behavior Patterns - Aligning user needs with sustainable practices
- Software and Architecture Patterns - Designing efficient applications
- Data Patterns - Implementing lifecycle policies and storage tiering
- Hardware Patterns - Using the minimum amount of hardware to meet your needs
- Development and Deployment Process - Optimizing development and testing environments
Questions
The AWS Well-Architected Framework provides a set of questions that allows you to review an existing or proposed architecture. It also provides a set of AWS best practices for each pillar.
SUS01 - How do you select Regions to support your sustainability goals?
View details →SUS02 - How do you take advantage of user behavior patterns to support your sustainability goals?
View details →SUS03 - How do you take advantage of software and architecture patterns to support your sustainability goals?
View details →SUS04 - How do you take advantage of data access and usage patterns to support your sustainability goals?
View details →SUS05 - How do you take advantage of hardware patterns to support your sustainability goals?
View details →SUS06 - How do you take advantage of development and deployment process to support your sustainability goals?
View details →AWS Services for Sustainability
AWS Customer Carbon Footprint Tool
Provides visibility into the carbon emissions associated with your AWS usage.
Amazon EC2 Auto Scaling
Helps ensure you have the correct number of instances available to handle your application load.
Amazon S3 Lifecycle Configurations
Automates moving objects to more cost-effective storage classes or deleting them.
AWS Graviton Processors
Deliver better price performance for your cloud workloads with lower energy consumption.
AWS Compute Optimizer
Helps you identify idle and underutilized resources.