updating archive and restore

logzio · Dec 12, 2023 · 32eea06 · 32eea06
1 parent e617083
commit 32eea06
Show file tree

Hide file tree

Showing 2 changed files with 34 additions and 36 deletions.
diff --git a/docs/shipping/AWS/aws-s3-bucket.md b/docs/shipping/AWS/aws-s3-bucket.md
@@ -128,12 +128,11 @@ Note that the ListBucket permission is set to the entire bucket and the GetObjec
 
 ##### Create a Logz.io-AWS connector
 
-In your Logz.io app, go to **Send your data**.
-Select the relevant AWS resource from the left menu.
+In your Logz.io app, go to **Integration hub** and select the relevant AWS resource.
 
-Click **+ Add a bucket** and select the option to **Authenticate with a role**
+Inside the integration, click **+ Add a bucket** and select the option to **Authenticate with a role**
 
-![Connect Logz.io to an AWS resource](https://dytvr9ot2sszz.cloudfront.net/logz-docs/log-shipping/s3-add-bucket-ids.png)
+![Connect Logz.io to an AWS resource](https://dytvr9ot2sszz.cloudfront.net/logz-docs/log-shipping/s3-bucket-id-dec.png)
 
 Copy and paste the **Account ID** and **External ID** in your text editor.
 
@@ -157,9 +156,9 @@ Go to your [IAM roles](https://console.aws.amazon.com/iam/home#/roles) page in y
 Click **Create role**.
 You're taken to the _Create role_ wizard.
 
-![Create an IAM role for another AWS account](https://dytvr9ot2sszz.cloudfront.net/logz-docs/aws/iam--create-role.png)
+![Create an IAM role for another AWS account](https://dytvr9ot2sszz.cloudfront.net/logz-docs/aws/create-role-main-screen-dec.png)
 
-Click **Another AWS account**.
+Click **AWS Account > Another AWS account**.
 
 Paste the **Account ID** you copied from Logz.io.
 

diff --git a/docs/user-guide/admin/give-aws-access-with-iam-roles.md b/docs/user-guide/admin/give-aws-access-with-iam-roles.md
@@ -62,12 +62,11 @@ Note that the ListBucket permission is set to the entire bucket and the GetObjec
 
 ### Create a Logz.io-AWS connector
 
-In your Logz.io app, go to **Send your data**.
-Select the relevant AWS resource from the left menu.
+In your Logz.io app, go to **Integration hub** and select the relevant AWS resource.
 
-Click **+ Add a bucket** and select the option to **Authenticate with a role**
+Inside the integration, click **+ Add a bucket** and select the option to **Authenticate with a role**
 
-![Connect Logz.io to an AWS resource](https://dytvr9ot2sszz.cloudfront.net/logz-docs/access-and-authentication/configure-s3-bucket.png)
+![Connect Logz.io to an AWS resource](https://dytvr9ot2sszz.cloudfront.net/logz-docs/log-shipping/s3-bucket-id-dec.png)
 
 Copy and paste the **Account ID** in your text editor.
 
@@ -82,49 +81,47 @@ Paste the policy in your text editor.
 
 Keep this information available so you can use it in AWS.
 
-### Create the IAM Role in AWS
+### Create the policy in AWS
 
-Go to your [IAM roles](https://console.aws.amazon.com/iam/home#/roles) page in your AWS admin console.
+Navigate to [IAM policies](https://us-east-1.console.aws.amazon.com/iam/home#/policies) and click **Create policy**.
 
-Click **Create role**.
-You're taken to the _Create role_ wizard.
+In the **JSON** tab,
+replace the default JSON with the policy you copied from Logz.io.
 
-![Create an IAM role for another AWS account](https://dytvr9ot2sszz.cloudfront.net/logz-docs/aws/iam--create-role.png)
+Click **Next** to continue.
 
-Click **Another AWS account**.
+Give the policy a **Name** and optional **Description**,
+and then click **Create policy**.
 
-Paste the **Account ID** you copied from Logz.io.
+Remember the policy's name—you'll need this in the next step.
 
-Select **Require external ID**,
-and then paste the following value into the **External ID** field: `Logzio:aws:extid:7d420c4cccf77013384751185ac12722`
+Return to the _Create role_ page.
 
-Click **Next: Permissions** to continue.
+### Create the IAM Role in AWS
 
-### Create the policy
+Go to your [IAM roles](https://console.aws.amazon.com/iam/home#/roles) page in your AWS admin console.
 
-In the  _Create role_ screen, click **Create policy**.
-The _Create policy_ page loads in a new tab.
+Click **Create role**.
+You're taken to the _Create role_ wizard.
 
-In the **JSON** tab,
-replace the default JSON with the policy you copied from Logz.io.
+![Create an IAM role for another AWS account](https://dytvr9ot2sszz.cloudfront.net/logz-docs/aws/create-role-main-screen-dec.png)
 
-Click **Review policy** to continue.
+Click **AWS Account > Another AWS account**.
 
-Give the policy a **Name** and optional **Description**,
-and then click **Create policy**.
+Paste the **Account ID** you copied from Logz.io.
 
-Remember the policy's name—you'll need this in the next step.
+Select **Require external ID**,
+and then paste the **External ID** from step 1.
 
-Close the tab to return to the _Create role_ page.
+Click **Next: Permissions** to continue.
 
 ### Attach the policy to the role
 
-Click refresh, and then type your new policy's name in the search box.
+Type the name of your new policy in the search box.
 
 Find your policy in the filtered list and select its check box.
 
-Click **Next: Tags**,
-and then click **Next: Review** to continue to the _Review_ screen.
+Click **Next** to review the new role.
 
 ### Finalize the role
 
@@ -215,7 +212,9 @@ Delete the configuration.
 If this is for an S3 fetcher, click **Add a bucket**,
 and click **Authenticate with a role**.
 
-![S3 fetcher and archive configuration screens](https://dytvr9ot2sszz.cloudfront.net/logz-docs/archive-and-restore/s3-fetcher-and-archive-config-external-id.png)
+<!-- ![S3 fetcher and archive configuration screens](https://dytvr9ot2sszz.cloudfront.net/logz-docs/archive-and-restore/s3-fetcher-and-archive-config-external-id.png)-->
+
+![Connect Logz.io to an AWS resource](https://dytvr9ot2sszz.cloudfront.net/logz-docs/log-shipping/s3-bucket-id-dec.png)
 
 Recreate your configuration with the values you copied in step 1,
 and copy the **External ID** (you'll paste it in AWS in the next step).
@@ -225,7 +224,7 @@ and copy the **External ID** (you'll paste it in AWS in the next step).
 Browse to the [IAM roles](https://console.aws.amazon.com/iam/home#/roles) page.
 Open the role used by the configuration you deleted in step 1.
 
-![IAM role summary page, trust relationships tab](https://dytvr9ot2sszz.cloudfront.net/logz-docs/aws/iam-role-edit-trust-relationship.png)
+![IAM role summary page, trust relationships tab](https://dytvr9ot2sszz.cloudfront.net/logz-docs/aws/logzrole-in-aws.png)
 
 Open the **Trust relationships** tab
 and click **Edit trust relationship** to open the policy document JSON.
@@ -305,7 +304,7 @@ Delete the configuration.
 If this is for an S3 fetcher, click **Add a bucket**,
 and click **Authenticate with a role**.
 
-![S3 fetcher and archive configuration screens](https://dytvr9ot2sszz.cloudfront.net/logz-docs/archive-and-restore/s3-fetcher-and-archive-config-external-id.png)
+![Connect Logz.io to an AWS resource](https://dytvr9ot2sszz.cloudfront.net/logz-docs/log-shipping/s3-bucket-id-dec.png)
 
 Recreate your configuration with the values you copied in step 1,
 and copy the **External ID** (you'll paste it in AWS later).