Some checks failed
check agents / check (push) Failing after 13s
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate stream from the individual and sub-agent patterns. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
82 lines
3.5 KiB
Markdown
82 lines
3.5 KiB
Markdown
---
|
|
name: aws-waf-sustainability
|
|
metadata:
|
|
category: WellArchitectedFramework
|
|
description: >-
|
|
Generates sustainability guidance for AWS workloads based on the
|
|
Sustainability pillar of the AWS Well-Architected Framework. Use when
|
|
choosing Regions, aligning resources to demand, or reducing the
|
|
environmental impact of an AWS workload.
|
|
---
|
|
|
|
# AWS Well-Architected Framework skill for the Sustainability pillar
|
|
|
|
## Overview
|
|
|
|
The Sustainability pillar covers understanding the impact of the services used,
|
|
quantifying it through the workload's lifecycle, and applying practices that
|
|
reduce it. AWS organizes it into Region selection, alignment to demand, software
|
|
and architecture, data, hardware and services, and process and culture.
|
|
|
|
## Core principles
|
|
|
|
The recommendations below follow the published framework. Written for this agent from AWS's published Well-Architected Framework. Question codes are AWS's.
|
|
|
|
- **Understand your impact**: Measure the workload's impact and model its
|
|
future. Grounding document:
|
|
https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html
|
|
|
|
- **Establish sustainability goals**: Set long-term goals, such as reducing
|
|
resources per transaction. Grounding document:
|
|
https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html
|
|
|
|
- **Maximize utilization**: Right-size so underlying hardware is used well.
|
|
Grounding document:
|
|
https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html
|
|
|
|
- **Anticipate and adopt new, more efficient hardware and software offerings**:
|
|
Keep designs flexible enough to adopt them. Grounding document:
|
|
https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html
|
|
|
|
- **Use managed services**: Share infrastructure across many customers.
|
|
Grounding document:
|
|
https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html
|
|
|
|
- **Reduce the downstream impact of your cloud workloads**: Reduce the energy or
|
|
resources customers need to use the service. Grounding document:
|
|
https://docs.aws.amazon.com/wellarchitected/latest/framework/sus-design-principles.html
|
|
|
|
## Relevant products
|
|
|
|
The following are _examples_ of products relevant to this pillar:
|
|
|
|
- **Compute**: AWS Graviton, AWS Lambda, AWS Fargate, Spot Instances
|
|
- **Data**: Amazon S3 Lifecycle, S3 Intelligent-Tiering
|
|
- **Measurement**: AWS Customer Carbon Footprint Tool
|
|
|
|
## Workload assessment questions
|
|
|
|
Ask appropriate questions to understand the requirements and constraints of the
|
|
workload and the organization. Choose from this list:
|
|
|
|
- SUS 1: How do you select Regions for your workload?
|
|
- SUS 2: How do you align cloud resources to your demand?
|
|
- SUS 3: How do you take advantage of software and architecture patterns to
|
|
support your sustainability goals?
|
|
- SUS 4: How do you take advantage of data management policies and patterns to
|
|
support your sustainability goals?
|
|
- SUS 5: How do you select and use cloud hardware and services in your
|
|
architecture to support your sustainability goals?
|
|
- SUS 6: How do your organizational processes support your sustainability goals?
|
|
|
|
## Validation checklist
|
|
|
|
Use this checklist to evaluate the architecture against this pillar:
|
|
|
|
- Region choice considers business requirements and sustainability goals.
|
|
- Resources scale to demand, and idle resources are removed.
|
|
- Asynchronous and scheduled work fits available capacity.
|
|
- Data lifecycle rules remove what is no longer needed.
|
|
- Efficient hardware and managed services are used.
|
|
- Metrics such as resources per transaction are tracked.
|