profile-aws-deploymentlisted

# Profile — AWS Deployment Opinionated cloud-deployment conventions for projects that deploy to AWS. Apply only when `PROJECT_BRIEF.md` → `## Profiles` lists `profile-aws-deployment`. ## Precedence `PROJECT_BRIEF.md` > this profile > model defaults. If the brief pins a different cloud provider or overrides any rule below, follow the brief and surface the conflict. ## Rules ### 1. AWS is the preferred cloud provider - When proposing or designing cloud deployment, default to AWS services unless `PROJECT_BRIEF.md` → `## Deployment` explicitly records a different provider. - If the brief already pins AWS, do not propose alternatives mid-feature — the decision is made. - For multi-cloud or hybrid projects, this profile's cost rule still applies to the AWS portion. ### 2. Every AWS suggestion MUST include a cost estimation table Any response, proposal, ADR, or design note that recommends, adds, or modifies AWS services **must** include a cost table. No exceptions — not even for "small" additions or "temporary" infrastructure. The absence of a cost table is grounds for the challenger to send **Request revision** (Major). **Prescriptive table format:** | Service | Usage assumption | Unit cost | Daily | Monthly | Yearly | Status | |---|---|---|---|---|---|---| | `<AWS service + SKU>` | `<concrete: hours, GB-months, req/s, GB-transfer>` | `<$ / unit>` | `$X.XX` | `$X.XX` | `$X.XX` | New / Pre-existing | | ... | | | | | | | | **Subtotal — new** | | | `<sum>` | `<sum>` | `<sum>