Beast configuration options
Use this information to know which Beast configuration options can be passed to the embedded web server in the Ceph configuration file for the Ceph Object Gateway.
Table 1 lists the Beast configuration options that can be passed to the embedded web server in the Ceph configuration file for the Ceph Object Gateway. Each option has a default value. If a value is not specified, the default value is empty.
Note: In
cephadm deployments, HTTPS is configured by using certificate management. These Beast SSL configuration options are not used for enabling HTTPS on the Ceph Object Gateway.| Option | Description | Default |
|---|---|---|
endpoint and ssl_endpoint |
Sets the listening address in the form address[:port] where the address is an IPv4 address string in dotted decimal form, or an IPv6 address in hexadecimal notation surrounded by brackets, [ ]. The optional port defaults to 8080 for endpoint and 443 for ssl_endpoint. It can be specified multiple times as in endpoint=[::1] endpoint=192.168.0.100:8000. |
EMPTY |
ssl_certificate |
Path to the SSL certificate file used for SSL-enabled endpoints. This option is not used for HTTPS configuration in cephadm deployments. |
EMPTY |
ssl_private_key |
Optional path to the private key file used for SSL-enabled endpoints. This option is not used for HTTPS configuration in cephadm deployments. |
EMPTY |
tcp_nodelay |
Performance optimization in some environments. | EMPTY |
Note: By default, the Beast front end writes an access log line recording all requests that are processed by the server to the RADOS Gateway log file.
Example /etc/ceph/ceph.conf file with Beast options using SSL
The following example shows legacy SSL configuration using Beast. This method is not used in cephadm deployments.
... [client.rgw.node1] rgw frontends = beast ssl_endpoint=192.168.0.100:443 ssl_certificate=<path to SSL certificate>