AWS Security ChangesHomeSearch

AWS wickr documentation change

Service: wickr · 2026-06-28 · Documentation low

File: wickr/latest/wickrio/troubleshooting.md

Summary

Updated broken links to point to correct logging documentation path and clarified GovCloud Docker image usage instructions

Security assessment

Changes involve documentation link fixes (wickrioguide → wickrio) and clarifying GovCloud Docker image usage. No security vulnerabilities or weaknesses are addressed. The GovCloud clarification prevents misconfiguration but doesn't mitigate security flaws.

Diff

diff --git a/wickr/latest/wickrio/troubleshooting.md b/wickr/latest/wickrio/troubleshooting.md
index 18f5d7350..f448dfe2f 100644
--- a//wickr/latest/wickrio/troubleshooting.md
+++ b//wickr/latest/wickrio/troubleshooting.md
@@ -602 +602 @@ Once the Wickr IO container is set up, it is designed to run indefinitely unless
-  * Look at Wickr IO client logs to identify the reason for crash. For more information, see [ Wickr IO clients logging](https://docs.aws.amazon.com/wickr/latest/wickrioguide/logging.html).
+  * Look at Wickr IO client logs to identify the reason for crash. For more information, see [ Wickr IO clients logging](https://docs.aws.amazon.com/wickr/latest/wickrio/logging.html).
@@ -617 +617 @@ Once you have a running bot client, you should be able to interact(depends on th
-  * If the client is running, then see the integration logs for any errors. For more information, see [ Wickr IO clients logging](https://docs.aws.amazon.com/wickr/latest/wickrioguide/logging.html).
+  * If the client is running, then see the integration logs for any errors. For more information, see [ Wickr IO clients logging](https://docs.aws.amazon.com/wickr/latest/wickrio/logging.html).
@@ -707 +707 @@ Possible causes:
-  * The bot is using the wrong Docker image for its deployment type (for example, the commercial image in or vice versa).
+  * The bot is using the wrong Docker image for its deployment type (for example, the commercial image in GovCloud or vice versa).
@@ -732 +732 @@ If `nslookup` fails, the host has a DNS resolution issue. If `curl` fails with a
-  5. Verify you are using the correct Docker image for your deployment type. Commercial deployments must use `wickrio/bot-cloud:latest`. deployments must use `wickrio/bot-cloud-govcloud:latest`. Using the wrong image causes the container to connect to the wrong messaging gateway, which results in a connection failure.
+  5. Verify you are using the correct Docker image for your deployment type. Commercial deployments must use `wickrio/bot-cloud:latest`. GovCloud deployments must use `wickrio/bot-cloud-govcloud:latest`. Using the wrong image causes the container to connect to the wrong messaging gateway, which results in a connection failure.