Can this be merged anytime soon? Really want to try quick.

I am on holiday right now, but I'll try to have a look.

Thanks for the PR! Much appreciated.

I finally had a look at the code.
First thing I want to confirm is about the port. You chose 80 as the default which works for you. Which port does your container listen on?
What I want to know is if the new task networking that fargate seems to use automatically uses the port you use inside your container.
So please let me know which port your container runs, if it's also port 80 or another one. And in case you change your container (app) port if it still works with port 80.

I found the answer.
An error occurred (ClientException) when calling the RegisterTaskDefinition operation: When networkMode=awsvpc, the host ports and container ports in port mappings must match.

So could you rewrite the code a little.
If the TaskDefinition has NetworkMode set to awsvpc (you have to confirm if that is the string, just my best guess), then use the private IP as you do now and set the container port as the port.

If the networking is bridge then do the same as current master branch, using the port mappings.

If you feel super motivated you could also add support for host networking by just using the instance IP + container port. (A mix of the other two)

Is this PR still alive? :)

Sorry, I've been busy. Will try to look at the suggestions this weekend.

We quickly declared virtualPort in line 118, just to accept different port we assign from variables, but we would really like to see @codesuki suggestions into the code 🤞

@anbotero Hi there. Recently I am exclusively using Google Cloud so I have no chance to test things on AWS.
If you want you can take over this PR, fix it up and I will merge it.