I have a project where users upload multiple 4-6MB AccessDb files to migrate into a AWS hosted SQL Server database. I think what is happening is that IIS maybe shutting down the process after some amount of time. 

Its basically a file upload and then a c# static class that reads the `mdb` file and uses EF .core to copy into SQL Server. Using Visual Studio, i don't see any shutdowns and all test files migrate successfully. 

Website built using .netcore 2.1 / c#

I have `Web.config` timeout set to `requestTimeout="00:59:00"` so that basically stops some 503 errors. 

What I'm seeing is that if all browsers are closed(or maybe not) and maybe technically no connections to IIS, that after a few minutes, the migration stops. I'm not seeing new rows added to the database.

I want my c# .netcore processes to continue migrating whatever databases the user uploaded without IIS or whatever other process killing the connection. 

Looking for tips I can update. I'm assuming there's other Web.config settings I can update?