100GB file transfer

How it works

At 1 Gbps in-region plan about 13 minutes. Across a 50 Mbps site link plan about 4.4 hours. Abort failed multipart uploads.

A 100 GB package stays in-region and finishes in under ten minutes. The same package pointed at the wrong continent misses the window and pays egress.

How it differs

Unlimited plans still review or throttle at this size.

A transcode started before complete reads a partial object.

Hash on the sending host. A laptop hash of 100 GB is its own job.

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 one hundred 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 one hundred 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.