I'm in the process of building some .NET Core based processes that will be running on several EC2 instances on AWS. Initially the thought was to just use a long running console app. But I started thinking it might be helpful to expose some Web API stuff so I can do stuff more easily remotely instead of locally on each box.

But I was concerned about how much extra CPU and Ram would be utilized by self hosting ASP.NET with Kestrel. I'm also curious if beyond an actual call to a Web API, would a process running as async task even be using Kestrel and/or any added bloat of ASP.NET itself?