Type of the load balancer used to route external traffic to ECS tasks hosted in Private Network

I am willing to deploy my backend Container on Amazon ECS , and I have gone through some of the questions asked here on AWS knowledge Center and am facing the same Issue as described here https://repost.aws/questions/QU6wyUfAxRSFyDLz1YEUlWag/deploying-ecs-task-definition-through-is-stuck-on-provisioning , and after checking the answer , it turned out that ECS Tasks have to be launched in a private Subnet with a NAT gateway to the Internet.

When hosting tasks that use the awsvpc network mode on Amazon EC2 Linux instances, your task ENIs aren't given public IP addresses. To access the internet, tasks must be launched in a private subnet that's configured to use a NAT gateway. For more information, see NAT gateways in the Amazon VPC User Guide. Inbound network access must be from within a VPC that uses the private IP address or routed through a load balancer from within the VPC. Tasks that are launched within public subnets do not have access to the internet.

so I have done that , but my ECS Task need to communicate with an RDS Instance hosted in another account , So I have set up VPC peering between both VPCs , and I expect that my backend logic will need to Interact with RDS Instance so , The task will need Inbound Connections from outside , and the task has to be set in a private subnet , and in this case it need to be attached to load balancer to route external traffic to the ECS Task as a target group . My question Is when I create a load balancer , what would be the type of the target group , In my case I need the load balancer to route the traffic to the ECS Task , so should I choose Instance type or Ipaddresses type taking into consideration that ECS tasks use networking in the AWS VPC to provide each task with its own elastic network interface and its own IP address.