Andrew Dunkman (he/him)

To reproduce, requires environment that has documentContents, which Flexion is blocked from getting until #682.

No longer happening in `migration` due to document contents no longer being present there.

Mike mentioned during a meeting today that lambda execution duration would also be good to see. It is reported through a Cloudwatch Metric automatically.

I can see Future Us wondering which service outages caused these 400s — do you have a link to your notes, or a list of when you saw this behavior?

Now that we have github issue templates, GitHub is directly picking up `docs/security.md` as our security policy: 

Duplicate of #638, @julialeague let me know if I’m incorrect!

Closing #638 instead.

If we had DNSSEC enabled, we could protect against issues such as #775 (only one set of records would be signed and authorized).

Search.gov has had [a rough experience with DNSSEC](https://digital.gov/2016/09/12/dnssec-vs-elastic-load-balancers-the-zone-apex-problem/), but it sounds like it would be significantly easier today now that Route53 supports DNSSEC, and the Tax Court is using Route53...

Enabling DNSSEC ([guide on how to do so on Route53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-configuring-dnssec.html)) is done in two steps: 1. Enable signing in Route53 for the hosted zone. 2. Add a `DS` record to...