CloudWatch Agent log file_path does not working on Windows Mount Point

The issue you're experiencing with CloudWatch Agent not being able to collect logs from Windows mount points is related to how the agent handles certain path types in Windows environments.

CloudWatch Agent has known limitations when dealing with non-standard Windows paths, including symlinks and mount points. The agent doesn't properly resolve these paths, which is why you're seeing the "system cannot find the path specified" error despite the path being valid and accessible through normal Windows operations.

Based on similar issues reported with symlinks, the CloudWatch Agent attempts to interpret the path literally rather than following the mount point to the actual location, causing path resolution problems.

Here are some potential workarounds you could try:

1. Create a simple copy job that copies the logs from the mount point to a standard folder path that CloudWatch Agent can access directly.

2. Try specifying the encoding parameter in your CloudWatch Agent configuration. Some users have reported success by explicitly setting the encoding (such as "UTF-8" or "UTF-16") in their configuration.

3. If the CloudWatch Agent service is having trouble with state information, you could try:

• Stopping the AmazonCloudWatchAgent service
• Deleting state files under "{Install_Directory}\AmazonCloudWatchAgent\Logs\state*"
• Editing your configuration file
• Restarting the service

4. Make sure you're using the latest version of the CloudWatch Agent, as some path handling issues may have been addressed in newer versions.

Unfortunately, if the mount point structure cannot be changed as you mentioned, and these workarounds don't resolve the issue, you might need to implement an alternative logging solution that can handle Windows mount points properly.
Sources
CloudWatch not resolving symlinks | AWS re:Post
Amazon CloudWatch Agent File Encodings Not Working | AWS re:Post