Synthetics: Not sure if best place for it (elastic#1597)

We should document the work around to ignore certificates. We should
also add a part about how to install the cert properly into the NodeJS
container, but I don't know about it.

---------

Co-authored-by: Mike Birnstiehl <[email protected]>
Co-authored-by: Vignesh Shanmugam <[email protected]>

Author: 3 people

solutions/observability/synthetics/cli.md

@@ -290,4 +290,8 @@ npx @elastic/synthetics totp <secret> --issuer <issuer> --label <label>
 :   Name of the provider or service that is assocaited with the account.
 
 `--label <string>`
-:   Identifier for the account. Defaults to `SyntheticsTOTP`
+:   Identifier for the account. Defaults to `SyntheticsTOTP`
+
+## Air-gapped environments
+
+When working in air-gapped environments, setup can become complex and require workarounds. One common issue is Node.js installations or containers not trusting custom certificates. To bypass certificate errors, prefix `npx` related commands with `NODE_TLS_REJECT_UNAUTHORIZED=0`. For example, `NODE_TLS_REJECT_UNAUTHORIZED=0 npx @elastic/synthetics init project-name`. This allows the command to bypass the certificate validations for all TLS connections.