| name | aws-service-minimum-viable |
|---|---|
| description | Minimal AWS wiring for Node services: runtime choice (Lambda, ECS, etc.), config/secrets, health checks, logs, optional Bedrock. Triggers on "deploy to AWS", "ECS", "Lambda API", "AWS healthcheck", "Bedrock client", "IAM for service". Always asks which AWS services, region, and whether Bedrock is in scope; suggests common defaults only after the user confirms per .cursor/rules/default-stack.md. |
- Ask the user before fixing compute shape: Lambda vs ECS/Fargate vs EKS vs Elastic Beanstalk, region, VPC constraints, and whether Bedrock is required (models, quotas, data residency). Defaults are suggestions, not decisions.
- Secrets — No secrets in git; Parameter Store / Secrets Manager / env from CI—confirm team standard.
- Observability — Follow
.cursor/rules/observability.mdfor logs/metrics/traces and health endpoints.
- Runtime — Match traffic, cold start tolerance, and team ops to Lambda vs container; document choice.
- IaC or console — If IaC exists in repo, extend it; otherwise propose smallest CDK/TF/CloudFormation slice and ask.
- Networking — Public ALB/API GW vs private; security groups; least-privilege IAM for runtime role.
- Deploy path — One-command or pipeline stage; rollback (previous task definition / alias).
- Bedrock (optional) — Only if user confirmed: model ID, inference profile vs foundation model, prompt/PII handling, retries and timeouts.
- Checklist: IAM actions needed, env vars, health URL, log group, alarms (if any).
- Open items: quotas, WAF, multi-AZ, cost caps.
.cursor/rules/default-stack.md,.cursor/rules/observability.md