> For the complete documentation index, see [llms.txt](https://docs.transparentedge.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.transparentedge.eu/integraciones/google-cloud-platform.md). # Google Cloud Platform A very evident use case is to place Transparent CDN in front of your Google Cloud Platform (GCP) infrastructure, even if you have the **Cloud CDN** service activated in GCP. Not only will you benefit from a wider range of CDN features, but you will also significantly reduce the cost of GCP. This cost reduction is mainly due to the fact that Transparent CDN offers lower rates for traffic compared to GCP, resulting in potential cost savings of 35-45% depending on the specific case. All of this is possible without making any changes to your AWS platform. All you need to do is configure the CNAME provided by AWS as the [origin](/getting-started/dashboard/auto-provisioning/sites.md) for Transparent CDN. ### Google Cloud Storage Similarly, just like you can configure Cloud CDN or your GCP auto-scaling platform by setting the CNAME of the service as the origin for Transparent Edge, you can do the same with **Cloud Storage.** By caching the content in Transparent Edge and serving all the objects from your Cloud Storage bucket through our edge locations, you can significantly reduce the traffic reaching Cloud Storage. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.transparentedge.eu/integraciones/google-cloud-platform.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.