From aafdb2a8c287e0dfc47e1c7a399027dcc4a04d73 Mon Sep 17 00:00:00 2001
From: Philipp Kahr <philipp.kahr@elastic.co>
Date: Wed, 4 Jun 2025 09:41:46 +0200
Subject: [PATCH 1/5] Not sure if best place for it

---
 solutions/observability/synthetics/cli.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/solutions/observability/synthetics/cli.md b/solutions/observability/synthetics/cli.md
index cd579ba422..d6a5aae367 100644
--- a/solutions/observability/synthetics/cli.md
+++ b/solutions/observability/synthetics/cli.md
@@ -290,4 +290,10 @@ 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`
\ No newline at end of file
+
+## Airgapped environments
+
+When we have to deal with airgapped environments we often endup in quite complicated setups and workarounds. Custom certificates are very common and might not be trusted by your NodeJS install or NodeJS container. To circumvent this and still make it work you can execute all `npx` related commands with `NODE_TLS_REJECT_UNAUTHORIZED=0` at the beginning. Thus creating a new project looks like this `NODE_TLS_REJECT_UNAUTHORIZED=0 npx @elastic/synthetics init project-name`. This will ignore any certificate errors.
+
+
+:   Identifier for the account. Defaults to `SyntheticsTOTP`

From ef39f6834bdaa13016abb3911b989b072c981a43 Mon Sep 17 00:00:00 2001
From: Philipp Kahr <philipp.kahr@elastic.co>
Date: Thu, 5 Jun 2025 11:05:12 +0200
Subject: [PATCH 2/5] Update solutions/observability/synthetics/cli.md

Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
---
 solutions/observability/synthetics/cli.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solutions/observability/synthetics/cli.md b/solutions/observability/synthetics/cli.md
index d6a5aae367..a5929f73ac 100644
--- a/solutions/observability/synthetics/cli.md
+++ b/solutions/observability/synthetics/cli.md
@@ -293,7 +293,7 @@ npx @elastic/synthetics totp <secret> --issuer <issuer> --label <label>
 
 ## Airgapped environments
 
-When we have to deal with airgapped environments we often endup in quite complicated setups and workarounds. Custom certificates are very common and might not be trusted by your NodeJS install or NodeJS container. To circumvent this and still make it work you can execute all `npx` related commands with `NODE_TLS_REJECT_UNAUTHORIZED=0` at the beginning. Thus creating a new project looks like this `NODE_TLS_REJECT_UNAUTHORIZED=0 npx @elastic/synthetics init project-name`. This will ignore any certificate errors.
+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 run even if the certificate isn't trusted.
 
 
 :   Identifier for the account. Defaults to `SyntheticsTOTP`

From db39989fac0c907844289b4927c3e7bba04e441b Mon Sep 17 00:00:00 2001
From: Philipp Kahr <philipp.kahr@elastic.co>
Date: Thu, 5 Jun 2025 11:05:17 +0200
Subject: [PATCH 3/5] Update solutions/observability/synthetics/cli.md

Co-authored-by: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
---
 solutions/observability/synthetics/cli.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solutions/observability/synthetics/cli.md b/solutions/observability/synthetics/cli.md
index a5929f73ac..ce25cae792 100644
--- a/solutions/observability/synthetics/cli.md
+++ b/solutions/observability/synthetics/cli.md
@@ -291,7 +291,7 @@ npx @elastic/synthetics totp <secret> --issuer <issuer> --label <label>
 
 `--label <string>`
 
-## Airgapped environments
+## 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 run even if the certificate isn't trusted.
 

From 78cdecf5ef3cbe6ae3854baf0ac12b57ec3ff10f Mon Sep 17 00:00:00 2001
From: Philipp Kahr <philipp.kahr@elastic.co>
Date: Thu, 5 Jun 2025 11:07:54 +0200
Subject: [PATCH 4/5] Update cli.md

---
 solutions/observability/synthetics/cli.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/solutions/observability/synthetics/cli.md b/solutions/observability/synthetics/cli.md
index ce25cae792..56cb086670 100644
--- a/solutions/observability/synthetics/cli.md
+++ b/solutions/observability/synthetics/cli.md
@@ -290,10 +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`
 
 ## 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 run even if the certificate isn't trusted.
-
-
-:   Identifier for the account. Defaults to `SyntheticsTOTP`

From 36b13456e338cdf4a889b1f2ba3d878b9d977dae Mon Sep 17 00:00:00 2001
From: Philipp Kahr <philipp.kahr@elastic.co>
Date: Thu, 5 Jun 2025 19:50:11 +0200
Subject: [PATCH 5/5] Update solutions/observability/synthetics/cli.md

Co-authored-by: Vignesh Shanmugam <vignesh.shanmugam22@gmail.com>
---
 solutions/observability/synthetics/cli.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solutions/observability/synthetics/cli.md b/solutions/observability/synthetics/cli.md
index 56cb086670..65e50a7e83 100644
--- a/solutions/observability/synthetics/cli.md
+++ b/solutions/observability/synthetics/cli.md
@@ -294,4 +294,4 @@ npx @elastic/synthetics totp <secret> --issuer <issuer> --label <label>
 
 ## 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 run even if the certificate isn't trusted.
+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.