Running Chef Infra Server for Canadian clients

I'm planning a Chef Infra Server setup for a few Canadian clients, and some of them need personal data and system details kept in Canada because of PIPEDA, plus stricter public-sector rules in BC and Quebec. Here's the checklist I'm working from. I'd like to hear what others would add.

  1. Run the Infra Server on hosts physically located in Canada, and confirm the provider's region in writing.
  2. Keep the PostgreSQL data, search index and cookbook storage on the same Canadian hosts or region.
  3. Back up the server (for example with knife-ec-backup or the built-in backup tooling) only to encrypted Canadian storage, with a clear retention period.
  4. Treat Ohai node attributes as sensitive, since they can include hostnames, IPs and user lists, and limit who can read them.
  5. Keep secrets in encrypted data bags or a vault hosted in Canada, never in plain cookbooks.
  6. Use per-user and per-org keys, rotate client keys, and keep the admin group small.
  7. Write down where every copy of node data, backups and logs lives, so clients can answer audit questions quickly.

For those running Chef Infra Server with residency requirements: how do you handle backups and node data so nothing leaves the country?

A practical addition: verify every supporting service, not just the Infra Server hosts. Chef Infra Server stores node objects and Ohai data in PostgreSQL and indexes them in OpenSearch, while cookbooks may live in bookshelf or external object storage; pin all of those to a Canadian region and document it. For backups, encrypt client-side before writing to Canadian storage, keep the encryption keys under Canadian control, and include a restore test in the retention process. Also check optional integrations such as Chef Automate, Supermarket, reporting/telemetry, and log shipping, since those are easy places for node data or metadata to leave the country unintentionally.