Support Akka Cluster that is split over several ECS Fargate services

[UrsMetz]

Is your feature request related to a problem? Please describe.

My team is evaluating Akka Cluster in an AWS Fargate cluster. The different components (that is separate applications running in Fargate) are spread over several Fargate services in the same ECS cluster.

As far as I understand AwsEcsDiscovery currently only covers the scenario where all components (i.e. the applications) are running inside the same Fargate service in different tasks: the lookup procedure searches for Fargate tasks for a specific ECS cluster and service. I guess that restriction stems from the fact that out of the box network communication in Fargate is only possible for tasks in the same service.

Describe the solution you'd like

We use a modified version of AwsEcsDiscovery that removes the restriction to a Fargate service (but are still evaluating whether that works). To allow the communication between tasks in different services we set up a hosted zone with internal DNS.

It would be nice if Akka.Management support that scenario out of the box.

Describe alternatives you've considered

The only alternative I currently see is some mixture of AWS queues or notification services (like SNS or SQS) and Akka (like Akka.Streams?). But that would require more infrastructure and makes running our application landscape locally more difficult and/or more distant from the cloud environment.