tweak docs for v1.3.8 (#791)

* tweak docs for v1.3.8

* push rest of develop script to repo

Author: Brian969

docs/installation/customization-index.md

@@ -57,7 +57,7 @@ Samples with Descriptions:
      - reduced various log retention periods and the VPCFlow log interval
      - removes the two example workload accounts
      - The most expensive individual component of this sample is the perimeter 3rd party firewalls 
-       - this example will be updated in the near future, removing the 3rd party firewalls
+       - this example will be updated in the v1.5.0 release, removing the 3rd party firewalls
        - we will add a NATGW for egress.  For ingress, customers will need to manually target the perimeter ALB to point to each backend-ALB's IP's and manually update the IP's when they change (the next major SEA code release will include functionality to automate this capability)
 
 ## 1.2. **Deployment Customizations**

docs/installation/installation.md

@@ -238,7 +238,7 @@ If deploying to an internal AWS employee account, to successfully install the so
 8. Add an `Email` address to be used for State Machine Status notification
 9. The `GithubBranch` should point to the release you selected
    - if upgrading, change it to point to the desired release
-   - the latest stable branch is currently `release/v1.3.7`, case sensitive
+   - the latest stable branch is currently `release/v1.3.8`, case sensitive
 10. Apply a tag on the stack, Key=`Accelerator`, Value=`PBMM` (case sensitive).
 11. **ENABLE STACK TERMINATION PROTECTION** under `Stack creation options`
 12. The stack typically takes under 5 minutes to deploy.
@@ -280,8 +280,6 @@ Issues in Older Releases:
 
 - New installs and upgrades to releases prior to v1.3.6 are no longer supported.
 
-- In v1.3.6 the Macie issue from v1.3.5 has been resolved, but Guardduty continues to cause the state machine to fail. Simply rerun the state machine. We are working on a fix.
-
 ## 2.6. Post-Installation
 
 1.  The Accelerator installation is complete, but several manual steps remain:
@@ -382,7 +380,7 @@ Issues in Older Releases:
    - The pipeline will automatically run and trigger the upgraded state machine
 9. If you are using a pre-existing GitHub token:
 
-- Update the Installer CloudFormation stack using the template downloaded in step 5, updating the `GithubBranch` to the latest release (eg. `release/v1.3.7`)
+- Update the Installer CloudFormation stack using the template downloaded in step 5, updating the `GithubBranch` to the latest release (eg. `release/v1.3.8`)
   - Go to AWS CloudFormation and select the stack: `PBMMAccel-what-you-provided`
   - Select Update, select Replace current template, Select Upload a template file
   - Select Choose File and select the template you downloaded in step 5 (`AcceleratorInstallerXYZ.template.json`)

reference-artifacts/Custom-Scripts/Developer-Scripts/README.md

@@ -0,0 +1,32 @@
+## AWS SEA Developer Script
+
+The script is intended for use by Accelerator developers to automate the generation of files required for LOCAL development.
+
+This script is a work in-progress and was designed for use by our development and test teams. This script grabs the latest outputs from an installed SEA environment from DynamoDB and stores them in the local/offline outputs.json file. ** Use at your own risk **
+
+## Requirements
+
+- This script requires the Accelerator to have completed one full/complete and successful state machine execution. It is NOT designed for use during the initial deployment process.
+- This script is written in Typescript, given the entire codebase is Typescript
+
+## Instructions
+
+1. Paste AWS temporary credentials (or set AWS_PROFILE) in the command terminal which will be used to execute the script
+
+2. Set the AWS_DEFAULT_REGION
+
+3. Execute the script `ts-node src/load-outputs.json`
+
+4. On successful execution, this script generates the file: `accelerator/src/deployments/cdk/outputs.json`
+
+## Use
+
+1. Install the Accelerator (with a full successful SM execution)
+2. Execute this script to populate the local outputs.json to enable local mode development
+3. Locally execute and test the code/Phase being modified (i.e. Phase1)
+4. Manually execute storeoutputs for the phase (i.e. Phase1)
+5. Re-run this script to update the local outputs.json file
+6. Execute or test other Phases (i.e. Phase2)
+
+Note: Steps 4 and 5 are only required if the executed Phase altered the outputs, if outputs remained identical, this is not required.
+

reference-artifacts/Custom-Scripts/Developer-Scripts/package.json

@@ -0,0 +1,21 @@
+{
+    "name": "@aws-accelerator/initial-script",
+    "version": "0.0.1",
+    "private": true,
+    "main": "src/index.ts",
+    "scripts": {
+      "lint:typecheck": "pnpx tsc --noEmit",
+      "lint:eslint": "pnpx eslint '{cdk,lib,src}/**/*.{js,ts}'"
+    },
+    "dependencies": {
+      "aws-sdk": "2.804.0"
+    },
+    "devDependencies": {
+      "@types/node": "14.14.31",
+      "esbuild": "0.11.18",
+      "ts-node": "9.1.1",
+      "typescript": "4.2.4"
+    },
+    "peerDependencies": {
+    }
+  }

reference-artifacts/Custom-Scripts/Developer-Scripts/src/index.ts

@@ -0,0 +1,7 @@
+{
+  "compilerOptions": {
+    "target": "es5",
+    "module": "commonjs",
+    "strict": true
+  }
+}