Rename Use_access_token_from_keycloak.md to Configuring_Scale_Accounts.md

Update publish.yml

.github/workflows/publish.yml

@@ -5,7 +5,7 @@ name: Upload to the upload server
 # Controls when the workflow will run
 on:
   push:
-    branches: [develop, main]
+    branches: develop
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
@@ -50,6 +50,7 @@ jobs:
         run: zip -r ${{ github.event.repository.name }}_${{ steps.tag_name.outputs.tag }}.zip . -x '*.git*' '*.idea*'
       - name: echo-step
         run: echo "${{ github.event.release.target_commitish }}"
+      
       - name: uploading archive to prod
         if: ${{ steps.branch_name.outputs.branch == 'main' || github.event.release.target_commitish == 'main'}}
         uses: wlixcc/SFTP-Deploy-Action@v1.0
@@ -58,8 +59,9 @@ jobs:
           server: ${{ secrets.SERVER }}
           ssh_private_key: ${{ secrets.SSH_PRIVATE_KEY }}
           local_path: ${{ github.event.repository.name }}_${{ steps.tag_name.outputs.tag }}.zip
-          remote_path: '${{ secrets.PROD_UPLOAD_URL }}'
+          remote_path: '${{ secrets.STG_UPLOAD_URL }}'
           args: '-o ConnectTimeout=5'
+          
       - name: uploading archive to staging
         if: ${{ steps.branch_name.outputs.branch == 'develop' || github.event.release.target_commitish == 'develop' }}
         uses: wlixcc/SFTP-Deploy-Action@v1.0
@@ -70,3 +72,4 @@ jobs:
           local_path: ${{ github.event.repository.name }}_${{ steps.tag_name.outputs.tag }}.zip
           remote_path: '${{ secrets.STG_UPLOAD_URL }}'
           args: '-o ConnectTimeout=5'
+

docs/Configuring_Scale_Accounts.md

@@ -1,8 +1,6 @@
-## Configuring ZIC To Use Access Token from Keycloak
-
 Zerto In-Cloud overcomes the AWS 20 concurrent snapshot copy limits between source and target regions by allowing you to use multiple AWS Accounts as Scale Accounts. Scale Accounts effectively multiply the number of concurrent snapshots that can be replicated for much lower RPOs.
 
-Use these steps to configure Zerto In-Cloud an IAM Policy and assign roles for ZIC Scale Accounts.
+Use these steps to configure a Zerto In-Cloud IAM Policy and assign roles for ZIC Scale Accounts.
 
 1.  Log into the scale account.
 2.  Navigate to **IAM - Policies**.

docs/Connecting_to_ZIC.md

@@ -0,0 +1,8 @@
+1.	Connect to ZIC using the URL [https://zic-ip-address](https://zic-ip-address) to validate it is online.
+2.	The installer will prompt you for a username and password. Log in with the username and password generated in the ZIC download page in myZerto.
+3.	The online installer will pull the latest code from myZerto and perform the installation.
+
+    ![Connect](Images/ZIC_connect_to_ZIC.png?raw=true)
+    
+4.  Log in using the default "admin" for both user and password for the first time.
+3.	At the prompt change the admin password.

docs/Deploying_the_ZIC_Instance.md

@@ -1,6 +1,6 @@
 # Deploying the ZIC Instance
 
-First you must Obtaining the Image Pull Key Secret. After you receive the email notification that your AWS Account ID was added to the privately published AMI, continue with the following configuration, deployment and installation steps.
+First you must obtain the image pull key secret. After you receive the email notification that your AWS Account ID was added to the privately published AMI, continue with the following configuration, deployment and installation steps.
 
 #### AWS Configuration