Problems mapping network drive during AWS Windows Packer build

I have a large installation folder (15+GB) which I need access to during a packer build in order to install an application (on AWS). Uploading this would take forever. We manually do this through mapping a network drive. I have setup an AWS Storage Gateway and can access the drive through an interactive logon session, however when I attempt to connect to it (“net use”) during the packer build it fails to connect (System Error 53 - Network Path not found). I think this has something to do with the “second hop” problem when accessing network resources via a remote connection. All solutions to the second hop problem involve configuring the share server which is not really possible when using a Storage Gateway on AWS. How do folks solve this issue typically? I have been beating my head against this for a while now and seems like there should be a straight forward solution to this but I am missing it. Any help would be appreciated.

Basic problem: How to access network files during a packer build