aboutsummaryrefslogtreecommitdiff
path: root/doc/book/cookbook/exposing-websites.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/book/cookbook/exposing-websites.md')
-rw-r--r--doc/book/cookbook/exposing-websites.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/book/cookbook/exposing-websites.md b/doc/book/cookbook/exposing-websites.md
index be462dc9..5f6a5a28 100644
--- a/doc/book/cookbook/exposing-websites.md
+++ b/doc/book/cookbook/exposing-websites.md
@@ -5,12 +5,14 @@ weight = 25
## Configuring a bucket for website access
-There are two methods to expose buckets as website:
+There are three methods to expose buckets as website:
1. using the PutBucketWebsite S3 API call, which is allowed for access keys that have the owner permission bit set
2. from the Garage CLI, by an adminstrator of the cluster
+3. using the Garage administration API
+
The `PutBucketWebsite` API endpoint [is documented](https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketWebsite.html) in the official AWS docs.
This endpoint can also be called [using `aws s3api`](https://docs.aws.amazon.com/cli/latest/reference/s3api/put-bucket-website.html) on the command line.
The website configuration supported by Garage is only a subset of the possibilities on Amazon S3: redirections are not supported, only the index document and error document can be specified.