Writing to AWS from a Windows legacy app that supports only Network Paths for exports?

Question

I have a legacy application running on Windows (on-premise) servers 
and I need to periodically back-up specific files on AWS.

The application supports natively only the "Network Path" for this periodic back-up:
is there any AWS storage I can access from on-premise via a Network path?

E.g. I believe something like this would be suitable for source legacy app (Windows based)
```
***\192.168.0.1\share ***

```

If there's a way to use UNC network path, even better
```
***\server-name\shared-resource-pathname***
```

Thanks!

PS: Already found S3 won't be suitable, from this old post
[https://stackoverflow.com/questions/28355537/amazon-s3-and-unc-paths](stack overflow)

What about EFS? 
Any other workaround that could be recommended if we don't want to access the files outside of the native application (to prevent conflict)

Yaniv Rozenboim · Answer

Have a look at [Amazon S3 File Gateway](https://docs.aws.amazon.com/filegateway/latest/files3/what-is-file-s3.html).

Amazon S3 File Gateway is a hybrid cloud storage service that provides seamless and secure integration between on-premises environments and Amazon S3. It allows organizations to store and retrieve files as objects in S3 using standard file protocols like NFS and SMB, making it easy to manage and access data with low-latency local caching while benefiting from the scalability and durability of S3.

Deeksha · Answer

Given your requirements and the need for compatibility with a legacy Windows application, Amazon FSx for Windows File Server is the most suitable option. It allows you to:

1. Use of UNC Paths: FSx for Windows File Server fully supports accessing file shares via UNC paths (\server-name\share), which is essential for seamless integration with your legacy application.

2. Integration with Existing Infrastructure: By integrating with your on-premise Active Directory, FSx ensures that you can maintain consistent user permissions and access controls, making it easy to manage.

3. Native Windows Compatibility: The SMB protocol support provided by FSx allows for straightforward file sharing and network drive mapping from your on-premise Windows servers.

4. Network Path Access: You can map a drive to the FSx file system using the network path (e.g., \fsx-filesystem-endpoint.amazonaws.com\share), enabling your legacy application to back up files directly to AWS without requiring significant changes.

Writing to AWS from a Windows legacy app that supports only Network Paths for exports?

Relevant content