> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart: Google Cloud to Scaleway

> Check Google Cloud-origin compatibility before selecting Scaleway as a target.

Cloud Adapter support is directional and service-specific. The Google Cloud service catalog does not list a Scaleway target. Use a cataloged Google Cloud route, or use the AWS-origin S3 route when your application can speak S3.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/tensor9/3qwgIru3kCfHriJC/images/diagrams/cloud-adapter-quickstart-google-cloud-to-scaleway-dark.svg?fit=max&auto=format&n=3qwgIru3kCfHriJC&q=85&s=0303b029e49f647b2d5c328e9efff3c4" alt="A Google Cloud to Scaleway route requires a directed service mapping before use." width="1100" height="360" data-path="images/diagrams/cloud-adapter-quickstart-google-cloud-to-scaleway-dark.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/tensor9/3qwgIru3kCfHriJC/images/diagrams/cloud-adapter-quickstart-google-cloud-to-scaleway-light.svg?fit=max&auto=format&n=3qwgIru3kCfHriJC&q=85&s=27332ae2ca74183b0ce4be41cc4c945b" alt="A Google Cloud to Scaleway route requires a directed service mapping before use." width="1100" height="360" data-path="images/diagrams/cloud-adapter-quickstart-google-cloud-to-scaleway-light.svg" />
</Frame>

## Start from the origin service

Name the exact Google Cloud API the application calls. For Cloud Storage, that includes JSON or XML protocol, object operations, generation conditions, compose, pagination, signed URLs, retention, lifecycle, and storage-class behavior. A Scaleway product with similar storage capabilities is not by itself a mapping for those semantics.

## Check published coverage

Use the [Google Cloud Service Catalog](/cloud-adapter/service-catalog/google-cloud/catalog). A supported target links to a detailed page that defines operations, fidelity, limitations, identity, migration, and target-specific behavior.

If Scaleway is not listed for the service, do not redirect a Google client to a generic object-storage endpoint. A successful TCP or HTTP connection does not establish Google API compatibility.

## Evaluate the application workload

Before choosing another route, capture the workload requirements:

1. Inventory the exact client library and API operations.
2. Record request fields, generation conditions, retries, and expected errors.
3. Create one uniquely named test object with known bytes and metadata.
4. Define native Scaleway verification for each mutation.
5. Include a missing-object and stale-precondition case.
6. Define cleanup after partial success or timeout.
7. Keep origin and target verification identities separate.

## What a supported route documents

| Area       | Required evidence                                                        |
| ---------- | ------------------------------------------------------------------------ |
| Protocol   | Google request parsing and authentication are documented.                |
| Operations | Every call in the fixture appears in the directed profile.               |
| Identity   | Origin caller and Scaleway runtime identities have distinct owners.      |
| State      | Generation, ETag, metadata, listing, and deletion semantics are defined. |
| Migration  | Existing objects, versions, and links have an explicit treatment.        |
| Recovery   | Uncertain writes, retries, cleanup, and rollback are testable.           |

Do not substitute an AWS S3 client for this fixture. It proves the AWS-origin protocol, not Google Cloud Storage behavior.

For a runnable Scaleway route, follow [AWS to Scaleway](/cloud-adapter/getting-started/aws-to-scaleway). For a Google Cloud-origin route, choose a supported target from the [Google Cloud catalog](/cloud-adapter/service-catalog/google-cloud/catalog).