Files
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
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>
2026-11-05 22:13:25 +00:00

84 lines
3.3 KiB
Markdown

---
name: aws-waf-cost-optimization
metadata:
category: WellArchitectedFramework
description: >-
Generates cost optimization guidance for AWS workloads based on the Cost
Optimization pillar of the AWS Well-Architected Framework. Use when
estimating, governing or reducing AWS spending, choosing pricing models or
planning data transfer.
---
# AWS Well-Architected Framework skill for the Cost Optimization pillar
## Overview
The Cost Optimization pillar is the ability to run systems that deliver business
value at the lowest price point. AWS organizes it into cloud financial
management, expenditure and usage awareness, cost-effective resources, managing
demand and supply, and optimizing over time.
## 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.
- **Implement Cloud Financial Management**: Invest in the capability to manage
cost. Grounding document:
https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html
- **Adopt a consumption model**: Pay only for what is used. Grounding document:
https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html
- **Measure overall efficiency**: Compare business output with the cost of
delivering it. Grounding document:
https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html
- **Stop spending money on undifferentiated heavy lifting**: Let managed
services take on operational work. Grounding document:
https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html
- **Analyze and attribute expenditure**: Identify usage and cost, and attribute
it to owners. Grounding document:
https://docs.aws.amazon.com/wellarchitected/latest/framework/cost-dp.html
## Relevant products
The following are _examples_ of products relevant to this pillar:
- **Visibility**: AWS Cost Explorer, AWS Budgets, AWS Cost Anomaly Detection,
cost allocation tags
- **Rates**: Savings Plans, Reserved Instances, Spot Instances
- **Sizing**: AWS Compute Optimizer, AWS Trusted Advisor
- **Data**: Amazon S3 Intelligent-Tiering, S3 Lifecycle
## Workload assessment questions
Ask appropriate questions to understand the requirements and constraints of the
workload and the organization. Choose from this list:
- COST 1: How do you implement cloud financial management?
- COST 2: How do you govern usage?
- COST 3: How do you monitor your cost and usage?
- COST 4: How do you decommission resources?
- COST 5: How do you evaluate cost when you select services?
- COST 6: How do you meet cost targets when you select resource type, size and
number?
- COST 7: How do you use pricing models to reduce cost?
- COST 8: How do you plan for data transfer charges?
- COST 9: How do you manage demand, and supply resources?
- COST 10: How do you evaluate new services?
- COST 11: How do you evaluate the cost of effort?
## Validation checklist
Use this checklist to evaluate the architecture against this pillar:
- Budgets, owners and anomaly alerts exist.
- Costs are tagged and attributed.
- Unused resources are found and decommissioned.
- Services were compared on cost.
- Sizing is based on measured use.
- Savings Plans or Spot are considered.
- Data transfer is estimated and designed for.
- Demand is managed with scaling, queues or throttling.