Neptune exporter tool to S3 running on Windows EC2

Question

Hi,
I'm running neptune exporter jar tool from a command prompt of a Windows EC2 istance. Everithing is ok until the time the tool has to write on the target s3 Bucket.
The tool seems to add a S3 suffix with the Windows path separtor so there is an error. This is the neptune export tool error:

Caused by: java.net.URISyntaxException: Illegal character in path at index 44: s3:///**
eptune-export.**

The S3 target bucket is setted in the path parameter as "outputS3Path":"s3:///".
The neptune-exporter tool adds **
eptune-export instead** of **/neptune-export** .

So i have two questions:
1) Is the neptune exporter tool not a Windows tool or there is a workround to escape the problem running on Windows prompt?
2) The copy to S3, from local folder, (**root-path** ) is at the end of all export process or there are more than one phase ?

Thank you

Andrea M.

re:Post Agent · Accepted Answer

Thank you for your questions about the Neptune exporter tool. Let me address your concerns:

1) The Neptune exporter tool is designed to work across different operating systems, including Windows. However, the issue you're experiencing with the path separator is a known limitation when running the tool on Windows. The tool seems to be using the Windows path separator ('\') instead of the forward slash ('/') required for S3 paths.

To work around this issue, you can try the following:

- Use forward slashes ('/') instead of backslashes ('\') in your JSON configuration file for all path-related parameters, including the outputS3Path.
- If possible, try using the Linux subsystem for Windows or a Unix-like environment on your Windows EC2 instance to run the Neptune exporter tool.

2) Regarding the copy process to S3, the Neptune exporter tool typically follows this workflow:

- It first exports the data to a local directory specified by the --root-path parameter.
- After the local export is complete, it then transfers the files from the local directory to the specified S3 bucket.

This two-step process allows for a more reliable export, as it first ensures that all data is properly exported locally before attempting to transfer it to S3. The copy to S3 is generally the final phase of the export process, occurring after all the data has been successfully exported to the local directory.

If you continue to experience issues, you might want to consider using the Neptune-Export service instead of the command-line tool. This service is designed to handle the export process more seamlessly and may avoid some of the path-related issues you're encountering.  
**Sources**  
[Using the neptune-export command-line tool to export data from Neptune - Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/export-utility.html)  
[Using the Neptune-Export service to export Neptune data - Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/export-service.html)

Neptune exporter tool to S3 running on Windows EC2

Relevant content