> NOTE:  While MinIO does not implement an upper boundary on buckets, your cluster's hardware has natural limits that depend on the workload and its scaling patterns. We strongly recommend [MinIO SUBNET](https://min.io/pricing) for architecture and sizing guidance for your production use case.

3389228,1,2014-03-28 13:52:56,2014-03-28 14:29:01,N,1,-73.950569152832031,40.792312622070313,-73.868507385253906,40.688491821289063,2,16.10,46,0,0.5,0,5.33,,,51.83,2,,75,63,green,0.04,0.0,0.0,62,37,5.37,1267,16...

		return req
	}

	testCases := []struct {
		request            *http.Request
		serverConfigRegion string
		expectedCode       APIErrorCode
	}{
		// Test case - 1.
		{createExpectedRequest(&http.Request{}, "eu-central-1"), globalMinioDefaultRegion, ErrNone},
		// Test case - 2.
		// In case of empty request body ErrNone is returned.
		{createExpectedRequest(&http.Request{}, ""), globalMinioDefaultRegion, ErrNone},
		// Test case - 3

- For [SSE-S3 or SSE-KMS encryption via KMS](https://min.io/docs/minio/linux/operations/server-side-encryption.html "MinIO KMS Guide"), all sites **must**  have access to a central KMS deployment. This can be achieved via a central KES server or multiple KES servers (say one per site) connected via a central KMS (Vault) server.

## Configuring Site Replication

- Configure an alias in `mc` for each of the sites. For example if you have three MinIO sites, you may run:

1020901 E MN09 Morningside Heights 3802 41 220 1 Manhattan 022000 1022000 E MN11 Central Harlem South 3803 3389527 2 2014-03-13 17:32:49 2014-03-13 17:39:48 N 1 -73.952896118164062 40.810546875 -73.954177856445313 40.800579071044922 1 0.73 5.5 1 0.5 0 0 7 2 1 166 41 green 0.00 0.0 0.0 32 18 14.09 1312 209.01 1 Manhattan 020901 1020901 E MN09 Morningside Heights 3802 1836 216 1 Manhattan 021600 1021600 E MN11 Central Harlem South 3803 3389528 2 2014-03-17 12:05:03 2014-03-17 12:09:49 N 1 -73.953781127929688...

                                                                └─────────┘
```

In a given setup, there are `n` MinIO instances talking to `m` KES servers but only `1` central KMS. The most simple setup consists of `1` MinIO server or cluster talking to `1` KMS via `1` KES server.