Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hello o/

We are integrating Flyte with AWS Batch on top of EKS using <https://github.com/flyteorg/flytekit/tree/master/plugins/flytekit-aws-batch/flytekitplugins/awsbatch|Flytekit Batch plugin>.
Flyte is registering an ECS job, which is the default orchestration type for EC2-platform-capability based jobs. But our queues point to EKS compute environments, and therefore fail at runtime giving the error `failed to execute handle for plugin [aws_array]: : Job Queue is attached to Compute Environment that cannot run ECS Jobs. status code: 400`

Are there any ways to explicitly tell Flyte to use EKS for the workflow/job? The <https://github.com/flyteorg/flytekit/blob/master/plugins/flytekit-aws-batch/flytekitplugins/awsbatch/task.py|Batch plugin AWSBatchConfig object> seems not to provide any mechanism to configure so.