Audit the foodoasis AWS account for billing alarms and budgets

[ale210]

Overview

We need to check the foodoasis AWS account 470363915259 for billing alarms and budgets, because it is the one member account nobody has looked at and it may be sending alerts that no one is acting on. Under our policy billing alerting belongs solely in the organization account, so anything found here should be removed.

Action Items

• Obtain read access to account 470363915259. This is the blocker — budgets cannot be listed cross-account from the payer account, so this genuinely needs credentials for the account itself. Nobody currently working on this has them. Find out who does and how access is granted before anything else here can start.
• List any AWS Budgets in the account: aws budgets describe-budgets --account-id 470363915259. Record the names, limits, notification thresholds, and subscribers — the equivalent budget in the incubator account was notifying an individual's personal Gmail address, so expect the subscriber list to matter as much as the thresholds.
• List any CloudWatch alarms, checking us-east-1 as well as whatever region the account normally uses, since billing metrics only exist in us-east-1.
• Check for Cost Anomaly Detection monitors and subscriptions: aws ce get-anomaly-monitors and aws ce get-anomaly-subscriptions.
• Report what was found in this issue, including "nothing" if that is the answer — a confirmed-clean account is a useful result and stops this being re-investigated later.
• Remove anything found, once the org-account budgets are live so there is no window with no coverage. Per-account visibility for foodoasis is provided by a LinkedAccount-filtered budget in the org account, created by the implementation issue.
• After removal, re-run the commands above and paste the empty output into this issue.

Note: there is no Terraform for this account, so this is console/CLI work rather than a PR, and verification is direct rather than post-merge.

Resources/Instructions

• Research and findings for the org and incubator accounts: Research - AWS billing alerts incubator#118 (see the findings comment)
• Implementation issue: Consolidate AWS billing alerting into the organization account #175
• Accounts: org/payer 504695638931 (hackforla), members 035866691871 (incubator) and 470363915259 (foodoasis). Org o-x3897m6l40, consolidated billing, FeatureSet ALL.
• Reason the org account cannot answer this itself: budgets are a per-account resource and are not enumerable from the payer account.