DelineaXPM · tylerezimmerman · Jan 16, 2024 · Jan 16, 2024 · Jan 16, 2024 · Jan 16, 2024
@@ -6,7 +6,7 @@ Add Disclaimer
 
 
 
-This scanner can help perform an Scan for Windows Systems based off an IP address range.
+This scanner can help perform a Windows Systems Scan based on an IP address range.
 
 
 
@@ -22,7 +22,7 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 - Fill out the required fields with the information
 
--  **Nmae:** (Evxample: AWS Tenant)
+-  **Name:** (Example: AWS Tenant)
 
 -  **Active:** (Checked)
 
@@ -52,7 +52,7 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 - Fill out the required fields with the information
 
--  **Nmae:** (Evxample: AWS IAM User)
+-  **Name:** (Example: AWS IAM User)
 
 -  **Active:** (Checked)
 
@@ -86,9 +86,9 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 - Fill out the required fields with the information from the application registration
 
-- Name: ( example -AWS IAM User Scaner)
+- Name: ( example -AWS IAM User Scanner)
 
-- Description: (Enter something meaningful to your Orgabization)
+- Description: (Enter something meaningful to your Organization)
 
 - Active: (Checked)
 
@@ -131,7 +131,7 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 -  **Input Template**: Manual Input Discovery
 
--  **Output Template:**: AWS Tenant (Use Temaplte that Was Created in the [SaaS Scan Template Section](#create-aws-tenant-scan-template
+-  **Output Template:**: AWS Tenant (Use the Template that Was created in the [SaaS Scan Template Section](#create-aws-tenant-scan-template
 
 - Click Save
 
@@ -161,23 +161,23 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 -  **Base Scanner:** PowerShell Discovery Create Discovery Script
 
--  **Input Template**: AWS Tenant (Use Temaplte that Was Created in the [AWS Tenant Scan Template Section](#create-aws-tenant-scan-template))
+-  **Input Template**: AWS Tenant (Use the Template that Was Created in the [AWS Tenant Scan Template Section](#create-aws-tenant-scan-template))
 
--  **Output Template:**: AWS IAM User (Use Temaplte that Was Created in the [AWS IAM Usert Scan Template Section](#create-account-scan-template))
+-  **Output Template:**: AWS IAM User (Use the Template that Was Created in the [AWS IAM Usert Scan Template Section](#create-account-scan-template))
 
--  **Script:** ServiceNow Local Account Scanner (Use Script Created in the [Create Discovery Script Section](#create-discovery-script))
+-  **Script:** AWS Local Account Scanner (Use the Script Created in the [Create Discovery Script Section](#create-discovery-script))
 
 -  **Script Arguments:**
 
-``` powershell
+``` PowerShell
 
 "IAMUser-Advanced" $[1]$AccessKey $[1]$SecretKey $[1]$Admin-Criteria $[1]$SVC-Account-Criteria
 
 ```
 
 - Click Save
 
-- This completes the creation of the ServiceNow Account Scanner
+- This completes the creation of the AWS Account Scanner
 
 
 
@@ -205,9 +205,9 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 - Click **Add Scanner**
 
-- Find the AWS Tenant Scanner or the Scanner Creatted in the [Create AWS Tenant Scanner Section](#create-aws-tenant-scanner) and Click **Add Scanner**
+- Find the AWS Tenant Scanner or the Scanner created in the [Create AWS Tenant Scanner Section](#create-aws-tenant-scanner) and Click **Add Scanner**
 
-- Select the Scanner just Ceated and Click **Edit Scanner**
+- Select the Scanner just completed and Click **Edit Scanner**
 
 - In the **lines Parse Format** Section Enter the Source Name (example: AWS Tenant)
 
@@ -217,27 +217,27 @@ This scanner can help perform an Scan for Windows Systems based off an IP addres
 
 - Click **Add Scanner**
 
-- Find the ServiceNow Local Account Scanner or the Scanner Creatted in the [Create SWS IAM User Scanner Section](#create-aws-iam-user-scanner) and Click **Add Scanner**
+- Find the AWS Local Account Scanner or the Scanner created in the [Create SWS IAM User Scanner Section](#create-aws-iam-user-scanner) and Click **Add Scanner**
 
-- Select the Scanner just Ceated and Click **Edit Scanner**
+- Select the Scanner just completed and Click **Edit Scanner**
 
 - Click **Edit Scanner**
 
 - Click the **Add Secret** Link
 
 - Search for the AWS Service Account Secret created in the [instructions.md file](../Instructions.md)
 
-- Check the Use Site Run As Secret Check box to enable it
+- Check the Use Site Run-As Secret Check box to enable it
 
-**Note Default Site run as Secret had to ne setup in the Site configuration.
+**Note Default Site run as Secret has to be set up in the Site configuration.
 
 See the [Setting the Default PowerShell Credential for a Site](https://docs.delinea.com/online-help/secret-server/authentication/secret-based-credentials-for-scripts/index.htm?Highlight=site) Section in the Delinea Documentation
 
 - Click Save
 
-- Click on the Discovery Source yab and Click the Active check box
+- Click on the Discovery Source tab and Click the Active check box
 
-- This completes the creation of theDiscovery Source
+- This completes the creation of the discovery Source
 
 
 
@@ -254,15 +254,15 @@ The AWS configuration is now complete. The next step is to run a manual discover
 
 - Click on **Network view**
 
-- Find the newly cretaed discocvery source and Users
+- Find the newly created discovery source and Users
 
 
 
 ## Optional Report
 
 
 
-In this section, There are instructions on how to create an optional report to display user information found in the discovery.
+In this section, There are instructions on creating an optional report to display user information found in the discovery.
 
 
 
@@ -311,4 +311,4 @@ GROUP BY d.ComputerAccountId, d.AccountName, d.CreatedDate
 ```
 - Click Save
 
-You will now find this report under the section you chose in the Category field.
+You will now find this report under the section you chose in the Category field.
@@ -1,6 +1,6 @@
  # AWS Connector Base Instructions
 
-This connectore provides the following functions  
+This connector provides the following functions  
 
 - Discovery of Local Accounts
 - Remote Password Changing users
@@ -12,39 +12,42 @@ This connector utilizes a Service Account alond with its Access Key and Secret.
 
 ### Prerequisites
 
-- Access to a AWS instance with administrative privileges. The administrattive privilleges may be replace with a lower security level, but these permissions must allow the Service Account to View and Manage all userss, biew all froup memberships and view all permission policiy assignments 
-- Installation of AWS Tools PowerShell module intsall on all Secret Server Distributed Engines.  For more information on AWS Tools click[here](https://www.powershellgallery.com/packages/AWS.Tools.IdentityManagement/4.1.483)
+- Access to a AWS instance with administrative privileges.
+  - These permissions must allow the Service Account to:
+    - View and Manage all users
+    - View all group memberships
+    - View all permission policiy assignments 
+- Installation of AWS Tools PowerShell module intsall on all Secret Server Distributed Engines that will be involved in RPC and Discovery processes.  For more information on AWS Tools click [here](https://www.powershellgallery.com/packages/AWS.Tools.IdentityManagement/4.1.483)
 
 ## Create AWS Service Account
 - Cunsult your AWS Administrator to create a user to be used as the Service Account.
 - Document the Accesss Key and Secret Key.  
-- Assign the persions detailed in the [Prerequisites Section](#prerequisites)
-
+- Assign the permissons detailed in the [Prerequisites Section](#prerequisites)
 
 
 ## Creating secret template for AWS Accounts 
 
 ### AWS User Account Template
 
-The following steps are required to create the Secret Template for ServiceNow Users:
+The following steps are required to create the Secret Template for AWS Users:
 
 - Log in to the Delinea Secret Server (If you have not already done so)
 - Navigate to Admin / Secret Templates
 - Click on Create / Import Template
 - Click on Import.
-- Cpoy and Paste the XML in the [AWS User Advanced.xml File](./Templates/AWS%20User%20Advanced%20Template.xml)
+- Copy and Paste the XML in the [AWS User Advanced.xml File](./Templates/AWS%20User%20Advanced%20Template.xml)
 - Click on Save
 - This completes the creation of the User Account template
 
 ### AWS Service Account Template
 
-The following steps are required to create the Secret Template for ServiceNow Privileged Account:
+The following steps are required to create the Secret Template for the AWS Privileged Account:
 
 - Log in to the Delinea Secret Server (If you have not already done so)
 - Navigate to Admin / Secret Templates
 - Click on Create / Import Template
 - Click on Import.
-- Cpoy and Paste the XML in the [AWS Service Account Advanced Privileged Template.xml File](./Templates/AWS%20Service%20Account%20Advanced%20Template.xml)
+- Copy and Paste the XML in the [AWS Service Account Advanced Privileged Template.xml File](./Templates/AWS%20Service%20Account%20Advanced%20Template.xml)
 - Click on Save
 - This completes the creation of the Privileged Account template
 
@@ -58,16 +61,16 @@ The following steps are required to create the Secret Template for ServiceNow Pr
 - Fill out the required fields with the information from the application registration
     - Secret Name (for example AWS Service Account )
     - The following field values are as created in the [Prerequisites Section](#prerequisites)
-    `- Username 
-    - Access Key
-    - Secret Key
-  - Admin-Criteria  - Cooma Seperted List of AWS Policies used to determine Admin Accounts (Policy Name=Policy arn
+      - Username 
+      - Access Key
+      - Secret Key
+  - Admin-Criteria  - Comma Seperted List of AWS Policies used to determine Admin Accounts (Policy Name=Policy arn
       example: Admin Access=arn:aws:iam::aws:policy/AdministratorAccess","Service-accounts,Custom Access=arn:aws:iam::aws:policy/CustomAccess" 
-  - SVC-Account-Criteria Cooma Seperted List of AWS Groups used to determine Service Accounts 
+  - SVC-Account-Criteria Comma Separated List of AWS Groups used to determine Service Accounts 
         example:  Service-Accounts1,ServiceAccounts2
   - Click Create Secret
   - This completes the creation of a secret in Secret Server for the ServiceNow Priviled Account
 
 ## Next Steps
 
-Once the tasks above are completed you can now proceed to creat a [Discovery Scanner](./Discovery/readme.md) and/or a [Remote Password Changer](./Remote%20Password%20Changer/readme.md)
+Once the tasks above are completed you can now proceed to create a [Discovery Scanner](./Discovery/readme.md) and/or a [Remote Password Changer](./Remote%20Password%20Changer/readme.md)
@@ -1,17 +1,16 @@
 # AWS Remote Password Changer
 
-**NOTE** AWS IAM User Password Changer does not support Heatbeats.If the password change fails an error will be reported
+**NOTE** AWS IAM User Password Changer does not support Heartbeats. If the password change fails an error will be reported
 
 ## Associate the Amazon IAM Console Password Privileged Account Remote Password Changer with the AWS IAM User template
 - Log in to the Delinea Secret Server
 - Navigate to Admin / Secret Templates
-- Click on the AWS User Advanced template create in the [instructions.md file](../Instructions.md)
+- Click on the AWS User Advanced template created in the [instructions.md file](../Instructions.md)
 - Click on Mapping
 - Click on Edit
 - Change the following field to use the Amazon IAM Console Password Privileged Account password type
     - Password Type to use: Select the Amazon IAM Console Password Privileged Account
 - Click on Save
--
 
 ## Associate scripting account to Azure AD secret
 To be able to correctly use the password changer, the AWS Service account must be associated with the AWS IAM User secret. This can be done by following the steps below:
@@ -20,13 +19,13 @@ To be able to correctly use the password changer, the AWS Service account must b
 - Locate your secret(s) based on the AWS IAM User template
 - Click on the secret
 - Click on Remote Password Changing
-- Go the Associated Secrets section in the bottom of the page
+- Go to the Associated Secrets section at the bottom of the page
 - Click on Edit
 - Click on Add Secret
-- Search for the earlier created [AW Service Accountsecret](../Instructions.md#create-secret-in-secret-server-for-the-aws-service-account) for the application registration and select that
+- Search for the earlier created [AWS Service Account secret](../Instructions.md#create-secret-in-secret-server-for-the-aws-service-account) for the application registration and select that
 - Click on Save
 
- This can Also bee done using a Secret Poicy assigned to the Parent Folder
+ This can also be done using a Secret Policy assigned to the Parent Folder
 
 ## Testing the configuration
 If all went well, you now should have:
@@ -39,23 +38,23 @@ If all went well, you now should have:
 - An Azure AD Account secret (not covered in this guide)
 - The application registration secret associated with the Azure AD Account secret
 
-To test the configuration, you can first start with performing a Heartbeat on the Azure AD Account secret. This can be done by following the steps below:
+To test the configuration, you can first start by performing a Heartbeat on the Azure AD Account secret. This can be done by following the steps below:
 - Log in to the Delinea Secret Server
 - Navigate to Secrets
 - Locate your secret(s) based on the Azure AD Account template
 - Click on the secret
 - Click on Heartbeat
-After a few moments the heartbeat should complete successfully.
+After a few moments, the heartbeat should complete successfully.
 
 To test the configuration, you can now change the password of the Azure AD Account secret. This can be done by following the steps below:
 - Log in to the Delinea Secret Server
 - Navigate to Secrets
 - Locate your secret(s) based on the Azure AD Account template
 - Click on the secret
 - Click on Change Password Now
-- Select Randoly Generated or Manual (and enter a password)
+- Select Randomly Generated or Manual (and enter a password)
 - Click on Change Password
 
 If there are any issues, please check the following:
 
-- SSDE.log on the Distributed Engine
+- SSDE.log on the Distributed Engine