Adventive — AWS Platform Standards

Evergreen standards, SOPs, and reference material for every AWS service Adventive uses. One folder per service. Time-bounded rollout work lives in projects/, not here.

Services

Service	Folder	Status
Secrets Manager	secrets-manager/	Stub — IdP recovery codes documented (incomplete); broader Secrets Manager use is pre-existing but undocumented here

Planned (add when needed)

• cognito/ — User pool configuration, sync, federation patterns
• s3/ — Bucket layout, lifecycle, access patterns (override-file storage in particular)
• ec2-ssm/ — EC2 + SSM patterns, AppDeploy successor
• rds-aurora/ — Aurora MySQL configuration, Hyperdrive-fronted access from Cloudflare
• iam/ — IAM role conventions, least-privilege patterns

Convention

Each service folder mirrors the docs/platform/cloudflare/ pattern:

<service>/
├── README.md                  What this service is, who owns it, status
├── 01-…05-…                   Numbered SOP sections in plain Markdown
├── Adventive_AWS_<Service>_SOP.pdf   WeasyPrint deliverable (added when SOP is complete)
└── (optional scaffolds)

Why a separate AWS platform tree

AWS has a meaningfully different operating surface from Cloudflare — IAM, AWS-native secret management, AWS CLI, CloudTrail audit, KMS — and warrants its own platform tree rather than being lumped under generic notes. This folder establishes the structure; specific service standards are added as they’re written.