Issue Summary

Artifacts produced on Windows build agents use the backslash character ( \ ) in the file names if the files are part of a hierarchy and thus this information is not preserved.
Object key naming conventions for S3 objects (https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html) recommend using the forward slash ( / ) character to preserve hierarchy information.
Currently Bamboo does not conform to the guidelines for naming.

Environment

• Windows remote agents

Steps to Reproduce

1. Enable the S3 artifact handler in Bamboo.
2. Run a plan that produces an artifact that is made of subdirectories and files (for example dir1\dir2\file.txt)
3. Use the produced artifact in another plan that runs on a Linux remote agent.
4. The artifact will be a file (for example dir1\dir2\file.txt) instead of a hierarchy.

Expected Results

The hierarchy information of the artifact is preserved in the file name using the forward slash.

Actual Results

The artifact is a file (for example dir1\dir2\file.txt) that uses a non-recommended character to represent hierarchical information. 

Workaround

Perform an additional step (with a script task) that archives the files produced by the build that are hierarchical. Define the resulting archive as the build artifact such that a single file is uploaded to the S3 bucket.
When using the artifact perform an extract step to recover the original hierarchy of the files.