> For the complete documentation index, see [llms.txt](https://docs.flashback.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flashback.tech/support-reference/supported-api-operations/cloud-storage/aws-s3-operations/s3-to-gcs-translation-issues.md).

# S3 to GCS translation issues

## Multipart Uploads

While GCS resumable uploads can be emulated without major problems using S3 multipart uploads, the opposite (emulating S3 multipart uploads using GCS resumable uploads) is not so straightforward.

The reason is that GCS resumable uploads have the following constraints:

* We must know the total size of the upload from the beginning, unlike S3 multipart. If we don't provide the total size, GCS API will assume it is a single chunk upload.
* The parts (or chunks) size must be a multiple of 256KiB (256\*1024 bytes).

To overcome those limitations, Flasback nodes emulate a S3 multipart upload sequence by treating each part as separate files, and when the client calls CompleteMultipartUpload, it combines all files in the final destination file.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flashback.tech/support-reference/supported-api-operations/cloud-storage/aws-s3-operations/s3-to-gcs-translation-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.