# What runs on your machines

Where a bucket's objects live, what the platform does with them on your behalf, what it can see, and how it fails.

Object Storage runs nothing on machines of yours, except for a bucket on your organization's own
hosts.

## Where the objects are

| Bucket                           | Where its objects are                                                                                                  |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| In a zone                        | the object store of that zone (`de1a`, `de1b`, `fi1a`)                                                                 |
| On a storage cluster             | the cluster's servers, in more than one building; with a remote copy, also the platform's object store in another zone |
| On your organization's own hosts | one copy on your hosts' object store                                                                                   |

Every request, from any S3 client, the console or the API, passes the platform's S3 gateway, which
checks the signature, your IAM policies, the key's scope and the bucket policy, and only then reads
or writes the object store.

## What the platform does on your behalf

- **Encryption:** every write gives the object store the bucket's data key, which encrypts the
  object; the data key is stored only wrapped by the platform key or your KMS key (see
  [Encryption](encryption.md)).
- **Replication and the remote copy:** the gateway queues every changed key; a worker copies it
  within seconds, and a full comparison of each replicating bucket runs once an hour. A copy that
  fails is tried again with growing pauses (30 seconds, then doubling up to an hour), eight times,
  before it is marked failed.
- **Lifecycle rules** are applied by the object store once a day.
- **Emptying a bucket** deletes on the bucket's storage directly, in batches of 100, many at once;
  each version is still checked against your policies and the bucket policy.
- **Integrity:** the platform checks buckets every day for entries the storage lists but cannot
  read (see [Troubleshooting](troubleshooting.md#a-bucket-shows-entries-storage-cannot-read)).
- **Usage** is measured for billing: the bytes in each bucket, every version counted, daily (on
  your own hosts every 15 minutes, rated daily).

## What the platform can see

Bucket names, object keys and sizes, and request metadata. The object store holds encrypted
objects; the platform can open the data key it wraps with the platform key, and needs your KMS key
for a bucket that uses one.

## How it fails

- A storage cluster keeps working with one server down; a whole building down stops writes with
  `503` and `Retry-After: 10`; see [Storage locations](storage-locations.md#when-a-part-fails).
- A write the object store refuses briefly is retried by the gateway, up to four attempts within
  40 seconds; if the store still answers `SlowDown`, you get `503 SlowDown`.
- A disabled KMS key makes the bucket refuse reads and writes within 30 seconds.

## Related

- [Storage locations](storage-locations.md)
- [Security](security.md)
