Add an S3 gateway #91
Comments
|
Agreed, its certainly planned (not only S3, but others as well...), I plan to make the deployment on aws as simple as possible. |
|
Implemented in the cloud plugin, closing. |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
Users can use their own endpoints for any ec2/s3 compatible API using: `cloud.aws.ec2.endpoint` or `cloud.aws.s3.endpoint` Closes #91. (cherry picked from commit f0fbea5)
vroyer
pushed a commit
to strapdata/elasticsearch
that referenced
this issue
Apr 26, 2017
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
New images optimised for local network
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we explicitly disable x-pack components that we don't want to benchmark (e.g. we disable ML when we want to benchmark Security). This allows us to merge elastic/rally-teams#6 because the configuration stays identical. Relates elastic/rally-teams#6 Relates elastic#91
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think S3 would be a perfect place to store metadata and index snapshots. It's reliable, scalable, cheap, and maintained by somebody else. And if you're running on ec2, it's pretty fast as well.
An S3 gateway would make deployment of a persistent elasticsearch cluster much easier, because there's no external configuration required (of a shared filesystem).
The text was updated successfully, but these errors were encountered: