You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expand the documentation for setting up Elasticsearch snapshots to include S3.
Use case. Why is this important?
Create automated snapshots (v2.2) documentation only includes an example for Google Cloud Storage (GCS). It would be helpful if there was also an example and directions for S3 both AWS and S3-compatable services. AWS' S3 is easier to set-up because it does not involve dealing with TLS settings that S3-compable services, such as MinioandCeph, that may use custom CAs.
By default Elasticsearch communicates with your storage system using HTTPS, and validates the repository’s certificate chain using the JVM-wide truststore. Ensure that the JVM-wide truststore includes an entry for your repository.
However, an example and directions for using Minio (the recommended non-AWS S3 provider for ECE) or another S3-compatable service with HTTPS and certificates is still needed.
The text was updated successfully, but these errors were encountered:
Proposal
Expand the documentation for setting up Elasticsearch snapshots to include S3.
Use case. Why is this important?
Create automated snapshots (v2.2) documentation only includes an example for Google Cloud Storage (GCS). It would be helpful if there was also an example and directions for S3 both AWS and S3-compatable services. AWS' S3 is easier to set-up because it does not involve dealing with TLS settings that S3-compable services, such as Minio and Ceph, that may use custom CAs.
There is elastic/elasticsearch#77081 to make managing the certificates easier for the repositories so users no longer need to edit the "JVM-wide trustore":
However, an example and directions for using Minio (the recommended non-AWS S3 provider for ECE) or another S3-compatable service with HTTPS and certificates is still needed.
The text was updated successfully, but these errors were encountered: