Enterprise Cloud Cost Optimization & Architecture Compliance

Here's the FinOps audit for the patient intake pipeline (Dev environment, HealthTech context detected via "patient" keyword — HIPAA/PHI safeguards applied).

Findings Summary

Remediation Diffs

1 & 2 — S3 bucket: tags + lifecycle policy

 resource "aws_s3_bucket" "patient_records" {
   bucket = "healthtech-patient-intake-records-dev"
+  tags = {
+    Owner       = "TBD"
+    CostCenter  = "TBD"
+    Environment = "dev"
+  }
 }
+
+resource "aws_s3_bucket_lifecycle_configuration" "patient_records" {
+  bucket = aws_s3_bucket.patient_records.id
+
+  rule {
+    id     = "healthtech-deep-archive-transition"
+    status = "Enabled"
+
+    transition {
+      days          = 90
+      storage_class = "STANDARD_IA"
+    }
+
+    transition {
+      days          = 365
+      storage_class = "DEEP_ARCHIVE"
+    }
+  }
+}

3 & 4 — EBS volume: gp3 + tags

 resource "aws_ebs_volume" "app_storage" {
   availability_zone = "us-east-1a"
   size              = 500
-  type              = "gp2"
+  type              = "gp3"
+  tags = {
+    Owner       = "TBD"
+    CostCenter  = "TBD"
+    Environment = "dev"
+  }
 }

5 & 6 — EC2 instance: right-size + tags + off-hours schedule

 resource "aws_instance" "pipeline_processor" {
   ami           = "ami-0c55b159cbfafe1f0"
-  instance_type = "m5.2xlarge"
+  instance_type = "t3.xlarge"

   tags = {
-    Name = "healthtech-intake-processor-dev"
+    Name        = "healthtech-intake-processor-dev"
+    Owner       = "TBD"
+    CostCenter  = "TBD"
+    Environment = "dev"
+    Schedule    = "OffHours"
   }
 }

Notes & Open Questions

Instance right-sizing: I defaulted m5.2xlarge → t3.xlarge (burstable, similar vCPU/RAM) since this is Dev. I don't have Datadog/CloudWatch utilization data — if this pipeline has sustained CPU-intensive workloads even in Dev, confirm before downsizing further, or a burst-credit-exhaustion issue could actually cost more in throttled reprocessing time.

• TBD tag values: fill in actual Owner/CostCenter values — I can't infer your org's cost-allocation taxonomy.
• Dollar estimates skipped per policy (no pricing CLI active) — impact is graded qualitatively above.

Want me to write these corrected files to your workspace?