Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Include reference to AWS VPC endpoints in s3 repository docs. #60654

Merged
merged 5 commits into from
Aug 5, 2020
Merged

[DOCS] Include reference to AWS VPC endpoints in s3 repository docs. #60654

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d6b5765
[DOCS] Include reference to AWS VPC endpoints in s3 repository docs.
vocatan Aug 4, 2020
e27fc7e
Add VPC endpoint as the recommended way of connecting to s3.
fcofdez Aug 5, 2020
53fbdb1
Update docs/plugins/repository-s3.asciidoc
fcofdez Aug 5, 2020
74c6a34
Update docs/plugins/repository-s3.asciidoc
fcofdez Aug 5, 2020
6ab59a3
Update docs/plugins/repository-s3.asciidoc
fcofdez Aug 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions docs/plugins/repository-s3.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -440,10 +440,12 @@ create the bucket then the repository registration will fail.

AWS instances resolve S3 endpoints to a public IP. If the Elasticsearch
instances reside in a private subnet in an AWS VPC then all traffic to S3 will
go through that VPC's NAT instance. If your VPC's NAT instance is a smaller
instance size (e.g. a t1.micro) or is handling a high volume of network traffic
go through the VPC's NAT instance. If your VPC's NAT instance is a smaller
instance size (e.g. a t2.micro) or is handling a high volume of network traffic
your bandwidth to S3 may be limited by that NAT instance's networking bandwidth
limitations.
limitations. Instead we recommend creating a https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html[VPC endpoint]
that enables connecting to S3 in instances that reside in a private subnet in an
AWS VPC. This will eliminate any limitations imposed by the network bandwidth of your VPC's NAT instance.

Instances residing in a public subnet in an AWS VPC will connect to S3 via the
VPC's internet gateway and not be bandwidth limited by the VPC's NAT instance.