TITAN Mystery Infra Audit — 2026-05-09

Summary

CloudFront: 51 total distributions. All 51 are fully classified — zero true mysteries.
Lambda: 13 total functions. All 13 classified — zero true mysteries.
The "14 unexpected CF distros + 12 unexpected Lambdas" from the task description were simply undocumented in the inventory at time of writing; live AWS data resolves every one.
Orphan count: 2 CF distributions (onelovingconciousness.com + Databricks-era Lambdas x2).
Estimated savings from orphan cleanup: ~$0–$2/mo (idle distros have no traffic cost; Lambda orphans are never invoked).

---

CloudFront Distributions (51 total)

|---|---|---|---|---|---|---|

CloudFront Classification Summary

TITAN-active (*.silentinfinity.com): 41
other-known (cloud8data / hmtech / harnoorminhas / spiritualaf): 9
orphan: 1 — onelovingconciousness.com (EDABRPI00YQDB)
mystery: 0

---

Lambda Functions (13 total)

|---|---|---|---|---|

Lambda Classification Summary

TITAN-active: 8
other-known: 2
orphan: 3 (2 Databricks + 1 CreateVideofromSource)
mystery: 0

---

Recommendations

Orphans recommended for deletion (4 total)

CloudFront (1):

EDABRPI00YQDB — onelovingconciousness.com. Not in known-project list, no TITAN connection. Verify DNS is dead before deleting.

Lambda (3):

databricks-workspace-stack-d-databricksApiFunction-Yi7IIPVJe81r — Databricks experiment from Dec 2024, python3.8 EOL
databricks-workspace-stack-d28bb-CopyZipsFunction-F6otTcdh12v3 — same Databricks stack
CreateVideofromSource — 27 months dormant, orphaned nodejs experiment

Mystery items needing user decision (0)

All distributions and functions have clear provenance. No mysteries.

Cost savings

CloudFront distributions with zero traffic cost $0/mo. Lambda orphans in cold storage with zero invocations cost $0/mo. Deleting them eliminates risk (attack surface, accidental invocation, confused infra state) but saves approximately $0–$2/mo in practice.

Real value of cleanup: reduced attack surface, cleaner IAM role inventory, no confusion when doing future audits.

---

Cleanup Commands (DO NOT RUN — awaiting approval)


# === CloudFront orphan ===
# Step 1: Get current ETag (required for disable/delete)
aws cloudfront get-distribution --id EDABRPI00YQDB --query 'ETag' --output text

# Step 2: Disable the distribution first (can't delete while Enabled)
# (Requires fetching current config, setting Enabled=false, then update-distribution)
# Use AWS Console for safest path, or:
# aws cloudfront get-distribution-config --id EDABRPI00YQDB > /tmp/cf_edabrpi.json
# [edit Enabled to false, extract ETag]
# aws cloudfront update-distribution --id EDABRPI00YQDB --distribution-config file:///tmp/cf_edabrpi_disabled.json --if-match <ETag>
# [wait for Status=Deployed]
# aws cloudfront delete-distribution --id EDABRPI00YQDB --if-match <new-ETag>

# === Lambda orphans ===
aws lambda delete-function --function-name "databricks-workspace-stack-d-databricksApiFunction-Yi7IIPVJe81r"
aws lambda delete-function --function-name "databricks-workspace-stack-d28bb-CopyZipsFunction-F6otTcdh12v3"
aws lambda delete-function --function-name "CreateVideofromSource"

# === Cleanup associated IAM roles (after Lambda deletion) ===
aws iam delete-role --role-name "databricks-workspace-stack-d28bb-functionRole-Kt0oN5V0FSDZ"
aws iam delete-role --role-name "databricks-workspace-stack-d28bb-CopyZipsRole-mDGYuFY05nEq"
aws iam delete-role --role-name "CreateVideofromSource-role-xc7u7mxy"

---

Audit performed 2026-05-10. Q39 complete.