Cross-border data transfers post-Schrems II: how did your team operationalize SCCs with US cloud providers?

We're a German SaaS provider processing EU citizen data. After Schrems II invalidated Privacy Shield, we migrated to Standard Contractual Clauses (SCCs) for all our US-based subprocessors (AWS, Datadog, Segment, HubSpot). The legal team signed the paperwork, but the operational reality is messier. Key challenges we've hit: - Transfer Impact Assessments (TIAs) are required per SCC Art. 2. Our first TIA was 40 pages. Updating it whenever a subprocessor changes their data handling is unsustainable. - The EU AI Act's data governance requirements (Art. 10) intersect with SCC obligations — training data transfers need both compliance tracks. - Some US subprocessors now offer 'EU data boundary' options, but the pricing is 2-3x higher. The business case is hard when the legal risk is theoretical vs. the cost is concrete. How has your team handled this in practice? - Do you automate TIA updates via subprocessor monitoring, or is it manual? - Any experience with supplementary measures (encryption in transit/at rest that effectively nullifies US government access claims)? - How do you balance the cost of EU-only infrastructure against the legal risk profile? Jurisdiction: EU/DE with US subprocessor relationships. Looking for operational experience, not legal opinions.