Sdms-977 'link'

Finding the entity responsible for the production.

| Component | Responsibility | Key Technologies | |-----------|----------------|------------------| | | Existing business logic, unchanged except for a thin “tier‑aware” abstraction layer. | Java 17, Spring Boot, Hibernate. | | Tier‑Management Service (TMS) | Evaluates policy DSL, decides tier, triggers move jobs, maintains lifecycle metadata. | Kotlin, Spring Cloud Stream (Kafka), Redis for short‑term state, PostgreSQL for policy store. | | Policy Store | Central repository of retention / archiving rules (versioned). | PostgreSQL, Flyway migrations. | | Object‑Mover Workers | Asynchronous workers that copy objects between storage back‑ends, verify integrity, update metadata. | AWS SDK v2, Azure SDK, custom Tape‑API client, Kotlin Coroutines. | | Audit & Compliance Logger | Immutable log of all tier‑change actions, signed with KMS. | Kafka topic sdms.tier.audit , AWS KMS, CloudTrail integration. | | Metrics & Alerts | Prometheus exporters for tier distribution, cost, latency; Grafana dashboards. | Prometheus, Grafana, Alertmanager. | sdms-977

| Concern | Mitigation | |---------|------------| | | All inter‑tier transfers use TLS 1.3; at‑rest encryption enforced via SSE‑KMS (AWS) / customer‑managed keys (Azure). | | Tamper‑evident audit | Audit events are signed with a KMS‑derived asymmetric key; logs are stored in an immutable S3 Object Lock bucket. | | Regulatory compliance | Policies map directly to legal retention tables (e.g., GDPR Art. 5(1)(e), HIPAA §164.308). | | Access control | Tier‑Management Service authenticates via service‑to‑service OAuth2 (client‑credentials) and checks role‑based permissions before issuing migrations. | | Disaster recovery | Each tier is replicated across at least two availability zones; cold‑tier (tape) is off‑site with a 30‑day retrieval SLA. | Finding the entity responsible for the production