> Note that anyone can access or delete master keys at `https://play.min.io:7373`. You should run your own KES
> instance in production.

## Configuration Guides

A typical MinIO deployment that uses a KMS for SSE-S3 looks like this:

```
    ┌────────────┐
    │ ┌──────────┴─┬─────╮          ┌────────────┐
    └─┤ ┌──────────┴─┬───┴──────────┤ ┌──────────┴─┬─────────────────╮

                                <div class="btn-group">
                                    <la:link href="/admin/dict" styleClass="btn btn-default btn-xs">
                                        <em class="fa fa-book">
                                        <la:message key="labels.dict_list_link"/>
                                    </la:link>
                                    <la:link href="list/1?dictId=${f:u(dictId)}"

                                        <la:link href="/admin/dict"
                                                 styleClass="btn btn-default btn-xs">
                                            <em class="fa fa-book">
                                            <la:message key="labels.dict_list_link"/>
                                        </la:link>
                                        <la:link href="../list/0/?dictId=${f:u(dictId)}"

                                        <la:link href="/admin/dict"
                                                 styleClass="btn btn-default btn-xs">
                                            <em class="fa fa-book">
                                            <la:message key="labels.dict_list_link"/>
                                        </la:link>
                                        <la:link href="../list/0/?dictId=${f:u(dictId)}"

                                        <la:link href="/admin/dict"
                                                 styleClass="btn btn-default btn-xs">
                                            <em class="fa fa-book">
                                            <la:message key="labels.dict_list_link"/>
                                        </la:link>
                                        <la:link href="../list/1?dictId=${f:u(dictId)}"

				scheme := "http"
				if r.TLS != nil {
					scheme = "https"
				}
				return scheme
			}(),
		}
	}
	return nil
}

// guessIsHealthCheckReq - returns true if incoming request looks
// like healthCheck request
func guessIsHealthCheckReq(req *http.Request) bool {
	if req == nil {
		return false
	}
	aType := getRequestAuthType(req)

                                        <la:link href="/admin/dict"
                                                 styleClass="btn btn-default btn-xs">
                                            <em class="fa fa-book">
                                            <la:message key="labels.dict_list_link"/>
                                        </la:link>
                                        <la:link href="../list/0/?dictId=${f:u(dictId)}"

      processCalled--; // don't count the tail invocation (makes tests a bit more understandable)
    }

    // ensures that the number of invocations looks sane
    void assertInvariants(int expectedBytes) {
      // we should have seen as many bytes as the next multiple of chunk after expectedBytes - 1

                                        <la:link href="/admin/dict"
                                                 styleClass="btn btn-default btn-xs">
                                            <em class="fa fa-book">
                                            <la:message key="labels.dict_list_link"/>
                                        </la:link>
                                        <la:link href="../list/0/?dictId=${f:u(dictId)}"

Now let's imagine these aren't "Concurrent Burgers", but "Parallel Burgers".

You go with your crush to get parallel fast food.

You stand in line while several (let's say 8) cashiers that at the same time are cooks take the orders from the people in front of you.