honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update repository-s3.asciidoc 

Documentation of AWS VPC public vs. private subnets and their affects on accessing S3.
This commit is contained in:
Ryan 2015-12-02 16:07:57 -08:00
parent ab45d69b16
commit 5890c9a813
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/plugins/repository-s3.asciidoc
View File

@ -388,3 +388,8 @@ To run test:
mvn -Dtests.aws=true -Dtests.config=/path/to/config/file/elasticsearch.yml clean test mvn -Dtests.aws=true -Dtests.config=/path/to/config/file/elasticsearch.yml clean test
---- ----
= AWS VPC Bandwidth Problems
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 your bandwidth to S3 may be limited by that NAT instance's networking bandwidth limitations.
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.