-
Notifications
You must be signed in to change notification settings - Fork 726
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.
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
Rewrite snapshot documentation and add CSP specific setups #5969
Conversation
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
|
||
== Periodic snapshots with a CronJob | ||
The AWS IAM roles for service accounts feature allows you to give Elasticsearch restricted access to a S3 bucket without having to expose and store AWS credentials directly in Elasticsearch. This requires you to run the ECK operator on Amazon's EKS offering and an https://www.elastic.co/guide/en/elasticsearch/reference/8.1/repository-s3.html#iam-kubernetes-service-accounts[Elasticsearch cluster running at least version 8.1]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this feature really allowing ES to impersonate an AWS IAM role, and therefore restrict access to an S3 Bucket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically yes, but I wanted to highlight the use case for it from the Elastic Stack side
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IRSA failed with a Service: Amazon S3; Status Code: 403; Error Code: AccessDenied;
when I try to create the snapshot repository, might be a PEBCAK error 🤷
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few minor editing suggestions, otherwise LGTM.
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
docs/orchestrating-elastic-stack-applications/elasticsearch/snapshots.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: Arianna Laudazzi <46651782+alaudazzi@users.noreply.github.com> Co-authored-by: Michael Montgomery <mmontg1@gmail.com> Co-authored-by: Michael Morello <michael.morello@gmail.com>
This refactors the existing snapshot documentation a bit removing obsolete sections (e.g. the cron job bit)
Adding new sections illustrating how to configure snapshot repositories on GCP and AWS using the CSP-specific IAM/service account integration on offer.
Adding a section about S3-compatible object stores and how to establish trust via a custom JVM trust store.
Fixes #5230
Fixes #5652