From e545a31a30c8d66671634e2c253b9460b1a3b9a3 Mon Sep 17 00:00:00 2001 From: Tanguy Leroux Date: Fri, 15 Jun 2018 12:20:05 +0200 Subject: [PATCH] [Docs] Remove reference to repository-s3 plugin creating an S3 bucket Closes #30910 --- docs/plugins/repository-s3.asciidoc | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/docs/plugins/repository-s3.asciidoc b/docs/plugins/repository-s3.asciidoc index bff64ebdc9186..6701d53c24047 100644 --- a/docs/plugins/repository-s3.asciidoc +++ b/docs/plugins/repository-s3.asciidoc @@ -284,22 +284,7 @@ You may further restrict the permissions by specifying a prefix within the bucke // NOTCONSOLE The bucket needs to exist to register a repository for snapshots. If you did not create the bucket then the repository -registration will fail. If you want Elasticsearch to create the bucket instead, you can add the permission to create a -specific bucket like this: - -[source,js] ----- -{ - "Action": [ - "s3:CreateBucket" - ], - "Effect": "Allow", - "Resource": [ - "arn:aws:s3:::snaps.example.com" - ] -} ----- -// NOTCONSOLE +registration will fail. [[repository-s3-aws-vpc]] [float]