|
7 | 7 |
|
8 | 8 | Bucket and Host Name |
9 | 9 | -------------------- |
10 | | -There are two different modes of accessing the buckets. The first (preferred) method |
11 | | -identifies the bucket as the top-level directory in the URI. :: |
| 10 | +There are two different modes of accessing buckets. The first method identifies |
| 11 | +the bucket as the top-level directory in the URI:: |
12 | 12 |
|
13 | 13 | GET /mybucket HTTP/1.1 |
14 | 14 | Host: cname.domain.com |
15 | 15 |
|
16 | | -The second method identifies the bucket via a virtual bucket host name. For example:: |
| 16 | +Most S3 clients nowadays rely on vhost-style access. The desired bucket is |
| 17 | +indicated by a DNS FQDN. For example:: |
17 | 18 |
|
18 | 19 | GET / HTTP/1.1 |
19 | 20 | Host: mybucket.cname.domain.com |
20 | 21 |
|
21 | | -To configure virtual hosted buckets, you can either set ``rgw_dns_name = cname.domain.com`` in ceph.conf, or add ``cname.domain.com`` to the list of ``hostnames`` in your zonegroup configuration. See `Ceph Object Gateway - Multisite Configuration`_ for more on zonegroups. |
| 22 | +The second method is deprecated by AWS. See the `Amazon S3 Path Deprecation |
| 23 | +Plan`_ for more information. |
22 | 24 |
|
23 | | -.. tip:: We prefer the first method, because the second method requires expensive domain certification and DNS wild cards. |
| 25 | +To configure virtual hosted buckets, you can either set ``rgw_dns_name = |
| 26 | +cname.domain.com`` in ``ceph.conf`` or add ``cname.domain.com`` to the list of |
| 27 | +``hostnames`` in your zonegroup configuration. See `Ceph Object Gateway - |
| 28 | +Multisite Configuration`_ for more on zonegroups. |
| 29 | + |
| 30 | +Here is an example of a ``ceph config set`` comamnd that sets ``rgw_dns_name`` |
| 31 | +to ``cname.domain.com``: |
| 32 | + |
| 33 | +.. prompt:: bash $ |
| 34 | + |
| 35 | + ceph config set client.rgw.<ceph authx client for rgw> rgw_dns_name cname.domain.dom |
| 36 | + |
| 37 | +.. tip:: You can define multiple hostnames directly with the |
| 38 | + :confval:`rgw_dns_name` parameter. |
| 39 | + |
| 40 | +.. tip:: When SSL is enabled, the certificates must use a wildcard in the |
| 41 | + domain name in order to match the bucket subdomains. |
| 42 | + |
| 43 | +.. note:: When Ceph Object Gateways are behind a proxy, use the proxy's DNS |
| 44 | + name instead. Then you can use ``ceph config set client.rgw`` to set the DNS |
| 45 | + name for all instances. |
| 46 | + |
| 47 | +.. note:: The static website view for the `s3website` API must be served under |
| 48 | + a different domain name. This is configured separately from |
| 49 | + :confval:`rgw_dns_name`, in :confval:`rgw_dns_s3website_name`. |
24 | 50 |
|
25 | | -.. tip:: You can define multiple hostname directly with the :confval:`rgw_dns_name` parameter. |
26 | 51 |
|
27 | 52 | Common Request Headers |
28 | 53 | ---------------------- |
@@ -111,3 +136,4 @@ Common Response Status |
111 | 136 | +---------------+-----------------------------------+ |
112 | 137 |
|
113 | 138 | .. _`Ceph Object Gateway - Multisite Configuration`: ../../multisite |
| 139 | +.. _`Amazon S3 Path Deprecation Plan`: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/ |
0 commit comments