update scripts remove date from arn and update healthcheck url

README.md

@@ -72,6 +72,7 @@ in the [LICENSE.txt](./LICENSE.txt) file in this repository.
     * [Development Machine Timezone Issues](#development-machine-timezone-issues)
     * [Linters & Pre-commit Hooks](#linters--pre-commit-hooks)
     * [Yarn install markdown-spell (aka mdspell)](#yarn-install-markdown-spell-aka-mdspell)
+  * [Manual Redeploys and Other Helpful Information in an Emergency](#manual-redeploys-and-other-helpful-information-in-an-emergency)
   * [PII Best Practices](#pii-best-practices)
     * [More about content dispositions](#more-about-content-dispositions)
     * [More about browser settings](#more-about-browser-settings)
@@ -606,6 +607,12 @@ yarn cache clean
 yarn global add markdown-spellcheck
 ```
 
+### Manual Redeploys and Other Helpful Information in an Emergency
+
+Like many modern software developers, we rely on a number of external services to be responsible for certain repeatable processes. One obvious example is CircleCI, which we use for deployment. It's a great tool in many ways, and reduces the surface area of what we ourselves have to manage, ideally transferring associated risk. However, it opens us up to a different risk: namely, what happens if CircleCI goes down and we need to deploy our app? For this circumstance, we have a series of scripts that can be run manually. They live in the script directory, and you can find information about how to run them [in this README under the Deployment Scripts heading](scripts/README.md#deployment-scripts).
+
+Please add any other fear-inducing scenarios and our mitigation attempts here.
+
 ### PII Best Practices
 
 Server side: any downloadable content passed to the client should by default have an inline content disposition (like PDFs).

scripts/README.md

@@ -50,7 +50,7 @@ These scripts are used to operate the system.
 ## Deployment Scripts
 
 This series of scripts allows you to quickly deploy the app manually (for example, should CircleCI be down).
-Run the scripts in this order with the environment you're deploying to (`exp`, `stg`, `prd`).
+Run the scripts in this order with the environment you're deploying to (`exp`, `stg`, `prd`) passed in as a variable.
 
 | Script Name             | Description                                                             |
 | ----------------------- | ----------------------------------------------------------------------- |