AWS iot-mi high security documentation change

Service: iot-mi · 2025-06-16 · Security-related high

File: iot-mi/latest/devguide/hub-log.md

Summary

Replaced curl command with AWS CLI command for configuring runtime logs, removing explicit exposure of AWS credentials in the example.

Security assessment

The original example exposed AWS access keys, secrets, and session tokens in plaintext, which poses a security risk. The updated AWS CLI method uses secure credential handling, mitigating potential credential leakage.

Diff

diff --git a/iot-mi/latest/devguide/hub-log.md b/iot-mi/latest/devguide/hub-log.md
index cb8cc57eb..848b4cd67 100644
--- a//iot-mi/latest/devguide/hub-log.md
+++ b//iot-mi/latest/devguide/hub-log.md
@@ -46,8 +46,3 @@ Configure the hub SDK log settings by calling the API to set up runtime log conf
-    curl \
-        --request PUT \
-        --location "api.iotmanagedintegrations.$AWS_REGION.api.aws/runtime-log-configurations/$ManagedThingId" \
-        --aws-sigv4 "aws:amz:$AWS_REGION:iotmanagedintegrations" \
-        --user "$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY" \
-        --header "x-amz-security-token: $AWS_SESSION_TOKEN" \
-        --header "Content-Type: application/json" \
-        --data '{ "RuntimeLogConfigurations": { "UploadLog": true, "LogLevel": "DEBUG" } }'
+    aws iot-managed-integrations put-runtime-log-configuration \
+        --managed-thing-id MANAGED_THING_ID \
+        --runtime-log-configurations LogLevel=DEBUG,UploadLog=TRUE