AWS Security ChangesHomeSearch

AWS kinesis-agent-windows documentation change

Service: kinesis-agent-windows · 2025-08-16 · Documentation low

File: kinesis-agent-windows/latest/userguide/troubleshooting-kinesis-agent-windows.md

Summary

Formatting changes including case correction ('AWS Services' to 'AWS services'), code formatting additions (backticks around service names), and section reference updates

Security assessment

Changes are typo corrections and markdown formatting improvements. The mention of 'security configuration issue' refers to existing troubleshooting guidance, not a new security disclosure or mitigation.

Diff

diff --git a/kinesis-agent-windows/latest/userguide/troubleshooting-kinesis-agent-windows.md b/kinesis-agent-windows/latest/userguide/troubleshooting-kinesis-agent-windows.md
index 6e5a6d739..983ab4819 100644
--- a//kinesis-agent-windows/latest/userguide/troubleshooting-kinesis-agent-windows.md
+++ b//kinesis-agent-windows/latest/userguide/troubleshooting-kinesis-agent-windows.md
@@ -5 +5 @@
-No Data Is Streaming from Desktops or Servers to Expected AWS ServicesExpected Data Is Sometimes MissingData Arrives in an Incorrect FormatPerformance IssuesOut of Disk SpaceTroubleshooting Tools
+No Data Is Streaming from Desktops or Servers to Expected AWS servicesExpected Data Is Sometimes MissingData Arrives in an Incorrect FormatPerformance IssuesOut of Disk SpaceTroubleshooting Tools
@@ -13 +13 @@ Use the following instructions to diagnose and correct issues when using Amazon
-  * No Data Is Streaming from Desktops or Servers to Expected AWS Services
+  * No Data Is Streaming from Desktops or Servers to Expected AWS services
@@ -28 +28 @@ Use the following instructions to diagnose and correct issues when using Amazon
-## No Data Is Streaming from Desktops or Servers to Expected AWS Services
+## No Data Is Streaming from Desktops or Servers to Expected AWS services
@@ -229 +229 @@ Replace `sourceId` with the value of the `Id` key-value pair of the `DirectorySo
-    2. Find the **AWSKinesisTap** service.
+    2. Find the **`AWSKinesisTap`** service.
@@ -231 +231 @@ Replace `sourceId` with the value of the `Id` key-value pair of the `DirectorySo
-    3. If the AWSKinesisTap service is not visible, install Kinesis Agent for Windows using the instructions in [Getting Started with Amazon Kinesis Agent for Microsoft Windows](./getting-started.html).
+    3. If the `AWSKinesisTap` service is not visible, install Kinesis Agent for Windows using the instructions in [Getting Started with Amazon Kinesis Agent for Microsoft Windows](./getting-started.html).
@@ -376 +376 @@ To resolve performance issues, perform the following steps:
-  3. Use the Windows performance monitor application to view Kinesis Agent for Windows metrics or stream those metrics to CloudWatch (see [Kinesis Agent for Windows Built-In Metrics Source](./source-object-declarations.html#kinesis-agent-builin-metrics-source)). In the Windows performance monitor application, you can add counters for Kinesis Agent for Windows sinks and sources. They are listed under the **AWSKinesisTap Sinks** and **AWSKinesisTap Sources** counter categories.
+  3. Use the Windows performance monitor application to view Kinesis Agent for Windows metrics or stream those metrics to CloudWatch (see [Kinesis Agent for Windows Built-In Metrics Source](./source-object-declarations.html#kinesis-agent-builin-metrics-source)). In the Windows performance monitor application, you can add counters for Kinesis Agent for Windows sinks and sources. They are listed under the **`AWSKinesisTap Sinks`** and **`AWSKinesisTap Sources`** counter categories.
@@ -457 +457 @@ If log files are being written, you can see output similar to the following:
-If no such output is occurring, then there is an application or service issue in writing the logs, or there is a security configuration issue rather than a problem with Kinesis Agent for Windows. If such output is occurring but Kinesis Agent for Windows is still not apparently processing the logs, see No Data Is Streaming from Desktops or Servers to Expected AWS Services.
+If no such output is occurring, then there is an application or service issue in writing the logs, or there is a security configuration issue rather than a problem with Kinesis Agent for Windows. If such output is occurring but Kinesis Agent for Windows is still not apparently processing the logs, see No Data Is Streaming from Desktops or Servers to Expected AWS services.