From 6582b849e0b8f0a2479777c256ece41a95335a8f Mon Sep 17 00:00:00 2001 From: Simplychee Date: Sat, 25 Nov 2023 19:34:42 +0200 Subject: [PATCH 01/25] updates --- .../admin/sso/google-workspace-sso.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/docs/user-guide/admin/sso/google-workspace-sso.md b/docs/user-guide/admin/sso/google-workspace-sso.md index ebdf4afe..291fc1dd 100644 --- a/docs/user-guide/admin/sso/google-workspace-sso.md +++ b/docs/user-guide/admin/sso/google-workspace-sso.md @@ -61,15 +61,18 @@ When [creating access groups for Google Workspace](https://support.google.com/a/ First, **[add a custom attribute](https://support.google.com/a/answer/6208725?hl=en)** and link it to your SAML app. -Open your SAML app, navigate to the **Add a new custom attribute** section, and add the following configuration: +Open your SAML app, navigate to the **SAML attribute mapping** section, and click **Configure SAML attribute mapping**. -* Name: groups -* Info type: Text -* Visibility: Visible to user and admin -* Number of values: Multi-value +In the **Attributes** section, add the custom attribute you've just created and set the app attribute of your choice. -![Set group SSO](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/google/add-custom-fields.png) +Next, you can add Group membership information by selecting the relevant groups from your account. -Next, configure the groups attribute to be sent across as part of the SAML login. +:::note +When using a Custom Attribute, you must update **every user** manually with a string. +::: + +![Set group SSO](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/google/google-sso-saml-group.png) + + \ No newline at end of file From 162f9385c9422575b17e47527295288434ec1aa0 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Sun, 26 Nov 2023 09:31:04 +0200 Subject: [PATCH 02/25] save --- docs/user-guide/admin/sso/google-workspace-sso.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/user-guide/admin/sso/google-workspace-sso.md b/docs/user-guide/admin/sso/google-workspace-sso.md index 291fc1dd..846830e5 100644 --- a/docs/user-guide/admin/sso/google-workspace-sso.md +++ b/docs/user-guide/admin/sso/google-workspace-sso.md @@ -73,6 +73,8 @@ When using a Custom Attribute, you must update **every user** manually with a st ![Set group SSO](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/google/google-sso-saml-group.png) +Click **Save** to apply the changes. + \ No newline at end of file From 6dc594fc27175e0bcb9eb35922ab525ff3239be1 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Sun, 26 Nov 2023 14:45:31 +0200 Subject: [PATCH 03/25] image --- docs/user-guide/admin/sso/google-workspace-sso.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/admin/sso/google-workspace-sso.md b/docs/user-guide/admin/sso/google-workspace-sso.md index 846830e5..34cde87d 100644 --- a/docs/user-guide/admin/sso/google-workspace-sso.md +++ b/docs/user-guide/admin/sso/google-workspace-sso.md @@ -65,14 +65,16 @@ Open your SAML app, navigate to the **SAML attribute mapping** section, and clic In the **Attributes** section, add the custom attribute you've just created and set the app attribute of your choice. -Next, you can add Group membership information by selecting the relevant groups from your account. - :::note When using a Custom Attribute, you must update **every user** manually with a string. ::: ![Set group SSO](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/google/google-sso-saml-group.png) +Next, you can add Group membership information by selecting the relevant groups from your account. + +![Set groups](https://dytvr9ot2sszz.cloudfront.net/logz-docs/sso-providers/google/group-membership.png) + Click **Save** to apply the changes. -### 2. Apply power search and filters +### Apply power search and filters You can control and limit which data you'd like to restore by applying **filters**, using **Power search**, or both. Your restored logs will only include data that matches all of your filters and your exact search term. @@ -128,7 +128,7 @@ If you want to remove one of the filters you've created, click on the **X** next -### 3. Restore your data +### Restore your data To continue, click on the **Proceed** button. You'll see a summary of your restore settings and be asked to approve them to continue the process. @@ -145,7 +145,7 @@ Once the restored account is ready, you'll receive a notification via email. Your restored account will remain available for 5 days. If you want to explore the data after the restore has expired, you'll have to restore it again. -### 4. Explore the restored account in OpenSearch Dashboards +### Explore the restored account in OpenSearch Dashboards You can view your restored account directly from the Restored accounts page by clicking on the **View logs** option next to the relevant account. diff --git a/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md b/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md index 95788c42..6d877ea0 100644 --- a/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md +++ b/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md @@ -115,4 +115,4 @@ Logz.io can archive and restore your logs with these credentials. Setting up your Power search permissions: -Once the new policy is updated, you'll be able to [use Power search](/user-guide/archive-and-restore/restore-archived-logs.html#apply-power-search) when restoring archived logs. \ No newline at end of file +Once the new policy is updated, you'll be able to [use Power search](/docs/user-guide/data-hub/archive-restore/restore-archived-logs#apply-power-search-and-filters) when restoring archived logs. \ No newline at end of file From 603213b63bce9988fe244ff375e6a72585801638 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Wed, 6 Dec 2023 13:44:15 +0200 Subject: [PATCH 24/25] permissions --- .../archive-restore/set-s3-permissions.md | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md b/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md index 6d877ea0..86958de2 100644 --- a/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md +++ b/docs/user-guide/data-hub/archive-restore/set-s3-permissions.md @@ -114,5 +114,44 @@ Logz.io can archive and restore your logs with these credentials. Setting up your Power search permissions: +1. Navigate to your AWS account and search for S3. + + ![Select S3](https://dytvr9ot2sszz.cloudfront.net/logz-docs/power-search/select-s3.png) + +2. Choose the relevant bucket on which you want to apply these permissions. **It should be the same bucket you've used when setting up your S3 permissions.** Once inside, click on Permissions, scroll down to **Bucket policy** and click on **Edit**. + + ![Select S3](https://dytvr9ot2sszz.cloudfront.net/logz-docs/power-search/permission-policy.png) + +3. Paste the following code inside the policy. **Replace the `XXX` with your bucket's name.** + + *If you don't have an existing policy, paste this code inside the editor. Otherwise, add this code to the bottom of the page.* + + ```yaml + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Principal": { + "AWS": "arn:aws:iam::406095609952:user/search-archive-restore-user" + }, + "Action": [ + "s3:GetObject", + "s3:ListBucket" + ], + "Resource": [ + "arn:aws:s3:::XXX", #replace XXX with your bucket's name + "arn:aws:s3:::XXX/*" #replace XXX with your bucket's name + ] + } + ] + } + ``` + + + ![Edit bucket policy](https://dytvr9ot2sszz.cloudfront.net/logz-docs/power-search/edit-bucket-policy.png) + +4. Click on **Save changes** to apply the new policy. It might take a few minutes for Logz.io to identify the new policy. + Once the new policy is updated, you'll be able to [use Power search](/docs/user-guide/data-hub/archive-restore/restore-archived-logs#apply-power-search-and-filters) when restoring archived logs. \ No newline at end of file From 01b6a71413aba864cbd4154207ba66aa531e16f6 Mon Sep 17 00:00:00 2001 From: Simplychee Date: Wed, 6 Dec 2023 13:50:39 +0200 Subject: [PATCH 25/25] link --- .../data-hub/archive-restore/restore-archived-logs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/data-hub/archive-restore/restore-archived-logs.md b/docs/user-guide/data-hub/archive-restore/restore-archived-logs.md index a39fa424..f5ac0425 100644 --- a/docs/user-guide/data-hub/archive-restore/restore-archived-logs.md +++ b/docs/user-guide/data-hub/archive-restore/restore-archived-logs.md @@ -85,7 +85,7 @@ Power search lets you apply a text search directly on your archived data before **Before using Power search:** -Power search requires [additional permissions](/user-guide/archive-and-restore/set-s3-permissions.html#add-power-search-permissions) to run. +Power search requires [additional permissions](/docs/user-guide/data-hub/archive-restore/set-s3-permissions/#add-power-search-permissions) to run.