We in Genpact see enough traction and importance and leverage Metaflow a lot in our POCs, and while going through one of the use-cases, @square-wire-39606, we found out the misconfiguration. I was playing through the example [https://github.com/outerbounds/terraform-aws-metaflow/tree/master/examples/eks_argo]. Since the UI module setup was not available for this use-case, I took the liberty to utilize the UI module available in the root directory(earmarked for the AWS Managed Services example) for the same. . In the readme.md file for module for the UI setup [github.com/outerbounds/terraform-aws-metaflow/blob/master/modules/ui/README.md] , it has been described to use AWS Resource IDs of Private subnets as the value for subnet1_id and subnet2_id(as visible in the attached image). The same configuration is getting leveraged in a the creation of an Application load balancer, this could not be the case as by concept, an internet facing AWS ALB should not utilize private subnets. Restricting the inbound traffic defeats the purpose of an Internet facing ALB.