5GB file transfer

How it works

Five gigabytes is 40,000 megabits. Multipart parts retry independently. A multipart ETag is not a whole-file MD5. Publish SHA-256.

Eight parts of a 5.0 GB dump average 80 Mbps and finish in about eight minutes. A single stream on the same path dies on a blip with nothing to resume.

How it differs

Five gigabytes is one object, not a folder.

Incomplete multipart uploads bill until you abort them.

Start the downstream job only after the complete call.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For five gb file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive five gb file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.