Hyp3 Deployment ReadMe Edits

[ZachHoppinen]

Adding in ReadMe clarifications and edits from my first hyp3 deployment.

Changes include:

• Added in overall motivation for setting up a hyp3 deployment
• clarify access key creation (I ended up doing this twice to rename and know where I would need to use it again)
• Clarify Warning about deploying ASF CI/CD stack
• Clarify formatting of editing asf.alaska.edu.db for SSL cert
• add example formats for all items in environment
• Clarify naming of github environment
• Add tip on deleting rolled back stack before re-running failed job
• clarify adding DNS record for API
• Add section on "Testing and adding user credits"
• Other small changes to make the flow actually match what you see on AWS

[jhkennedy]

Suggested change

	3. Add tag value to describe the key such as `hyp3-foobar-access`
	3. (Optional)Add tag value to describe the key, such as "For GitHub Actions CI/CD pipelines"

[jhkennedy]

Suggested change

	Then copy past the add the validation record to a row of
	https://gitlab.asf.alaska.edu/operations/puppet/-/edit/production/modules/legacy_dns/files/asf.alaska.edu.db
	(see previous records for examples).
	in the format `<CNAME_name> in CNAME <CNAME_value>.` (see previous records for examples).
	Then create a validation record in
	https://gitlab.asf.alaska.edu/operations/puppet/-/edit/production/modules/legacy_dns/files/asf.alaska.edu.db
	of the form `<CNAME_name> in CNAME <CNAME_value>`, stripping the `.asf.alaska.edu` from the CNAME name (see previous records for examples).

[jhkennedy]

Suggested change

	You will need to add the deployment to the matrix in an existing GitHub Actions `deploy-*.yml` workflow (.github/workflows/) or create
	You will need to add the deployment to the matrix in an existing GitHub Actions `deploy-*.yml` workflow located in the `.github/workflows/` directory, or create

[jhkennedy]

Suggested change

	existing workflows, and then updating all of the fields.
	existing workflows, and then updating all of the fields

[jhkennedy]

Suggested change

	After successful deployment and DNS record merging you can test you deployment by accessing the Swagger UI and using the POST /user tab to
	After successfully deploying HyP3 and your new DNS record has taken effect (or you've edited your local DNS name resolution), you can test your deployment by accessing the Swagger UI and using the POST `/user` tab to

[jhkennedy]

Suggested change

	You can then return the Swagger UI and use the POST /jobs to run a test job and confirm it completes.
	You can then return the Swagger UI and use the POST `/jobs` to run a test job and confirm it completes.

[jhkennedy]

Suggested change

	check if your user is approved and has credits for running jobs on the deployment. This should automatically add your user to the DynamoDB
	table.
	AWS console -> DynamoDB -> Explore items
	1. Find the table with format like `hyp3-foobar-UsersTable-XXXXXXXXXXXXX`
	2. Edit your user (only present after using the Swagger UI in some way)
	3. Add credits if neccessary
	check if your user is approved and has credits for running jobs on the deployment. You will need to be authenticated by either providing an Earthdata Login Bearer Token using the "Authorize" button, or by having a valid `asf-urs` cookie, typically logging into [Vertex](https://search.asf.alaska.edu). Interacting with HyP3 should automatically add your user to the DynamoDB table with the default number of credits (typically 0).
	To add credits to your (or any) user, log in to the AWS console and navigate to DynamoDB -> Explore items, then:
	1. Find the table with a format like `hyp3-foobar-UsersTable-XXXXXXXXXXXXX`
	2. Edit your user record (only present after using the Swagger UI in some way)