Hmmm... shouldn't we have a header here, eg. "Self-hosting a keyserver on AWS"?

If we add that, I think all the headers should go down a level, eg. ## -> ###

We have several prerequisites for running the scripts and Terraform logic that will help you manage your keyserver on AWS.

These prerequisites are all packaged together in our provided Nix development shell.

It's weird that this is a subsection of "Create development shell". Can you rethink the "Table of Contents" here?

Not sure we need these lines

What does "entered past" mean?

Weird that the next line has a : but this line doesn't

Nit: I'd drop the trailing slash

I don't see what touch is doing here. I can't think of a text editor that cares whether a file exists prior to being edited. Why not just use vim, and suggest the user substitute with their desired text editor? You could also use $EDITOR

What's this mean? What it explained earlier?

Don't think we need this line

It's optional, right?

I think we can remove this line

Can we separate out the line of code?

Think "above specified" is obvious

Don't we need more configs? How about all the license keys? I believe that I documented somewhere on Linear the list of params that I thought we needed on keyserver vs. web vs. landing... can you dig up that Linear comment, and try to make sure you cover everything the keyserver needs?

Not all variables need to be modified, right? Eg. the CORS config

It's weird to use inline code formatting for a separate line of code. Why not use the same three-backticks approach you use directly above?

I thought ALIAS was non-standard. Don't some domain registrars frame this as a CNAME at the root? Do we need to explain the requirement of support for the non-standard ALIAS / root CNAME record earlier?

This might have been a misunderestanding. Create a development shell is just a comment. Removing it because The Nix development shell can be run with: is right above and the comment isn't necessary.

Better word here wouldn've been skipped. Including in next rebase

Going to keep this consistent by always include :

Good point. This is specific to my habits. Going to just replace with suggesting they use their own desired text editor

This rightfully could be confusing. Original instructions didn't have users set a region if they were using export to use their aws credentials. I'm going to change prior instructions to just require setting AWS_REGION by default.

Currently not optional. terraform apply needs access to MariaDB to initialize the Comm database

ALIAS is non-standard. I'll include a comment above about the need for ALIAS and root CNAME records with a recommendation to configure dns rules through route53 if their domain registrar does not support these records