You are building and running client applications in Cloud Run and Cloud Functions. Your client requires that all logs must be available for one year so that the client can import the logs into their…

Updating all application images and functions to send logs to two different destinations would require significant code changes, violating the requirement to minimize code changes.

While Pub/Sub can be an intermediary, a dedicated Cloud Logging logs bucket provides a more direct and managed solution for long-term log retention and is automatically integrated with Cloud Logging, simplifying the solution.

Creating a general Cloud Storage bucket requires additional configuration for log management and implies code changes for applications to write directly, and VPC firewall rules are generally not relevant for Cloud Run/Functions logging.

Cloud Run and Cloud Functions automatically send logs to Cloud Logging, requiring no code changes. By creating a dedicated Cloud Logging logs bucket with a 365-day retention policy and configuring a logging sink to route the logs there, you satisfy the one-year retention requirement using managed services while minimizing application code changes.