diff --git a/tools/creating-new-drutopia-site.md b/tools/creating-new-drutopia-site.md
index 4c3be3e..e70fab0 100644
--- a/tools/creating-new-drutopia-site.md
+++ b/tools/creating-new-drutopia-site.md
@@ -140,3 +140,29 @@ git commit -m "Update composer lock file"
 git push
 cd -
 ```
+
+### Finalize hosting setup
+
+#### HTTPS Certificates
+
+First, ensure that all domain names are pointed to the new location. Deploy the site with the appropriate `server_hostname`, and `server_aliases` already set. Note that if `canonical_redirect: true` you should use the default `<member>-live.drutopia.org` for `server_hostname` until the certificate is provisioned.
+
+Currently, acquiring the certificates must be peformed directly on the server (as root) by running:
+`certbot certonly --webroot -w /home/<member>/site/web -d example.org -d www.example.org -d example-live.drutopia.org`
+
+Adjust the vault configuration to include the path to the newly generated cert and key values in the SSL settings for the member (`site_ssl_cert_path` and `site_ssl_key_path`). If there are no further changes, an `ahoy deploy-site-minimal <member>` deployment is enough to activate the certificates (if host names have been added, a normal deploy is necessary for them to reach Drupal's setting for allowed hostnames).
+
+#### Reconfigure For Future Deployments
+
+Once the initial site has been installed, be sure to update the vault parameters, as appropriate:
+
+```
+config_import: true
+drupal_install: False (or else remove this line)
+```
+
+#### Potential Traps
+
+If configuration is not importing: log in as root and delete the file `/home/<member>/site/CUSTOM-VERSION` and run the config-forced install option again - this tells the activate script to repopulate the config folder from the custom source.
+
+See (this issue)[https://gitlab.com/drutopia-platform/drutopia_host/-/issues/18) for the latest status on this problem.