Vehicles will send files over unreliable cellular links; current FTP restarts transfers on failure. To improve reliability and minimize transfer time for ETL ingestion, what should you do?

Directly uploading files to Regional Cloud Storage buckets via Google APIs over HTTPS is the best solution. HTTPS provides built-in reliability and retry mechanisms, making it suitable for unreliable cellular links. Regional buckets offer lower latency for uploads within their respective regions, which is crucial for minimizing transfer time. The ETL process can then access these regional buckets. Using FTP, even with GKE clusters, is problematic because FTP lacks inherent retry mechanisms for partial failures, leading to restarts and increased transfer times. Multi-Regional buckets are more expensive and offer global availability, which isn't strictly necessary if data is primarily consumed within its region of origin before ETL. While Multi-Regional buckets could work, Regional buckets are more cost-effective and performant for this specific scenario.