ECS Patterns missing Service Connect configuration

[atomicHamsters]

I'm building IaC for a web application in ECS comprised of multiple services communicating via Service Connect. The client service, which still uses Service Connect to make database calls, is behind a public ALB.

For back-end services, the FargateService construct provided a configuration property to enable Service Connect. So far so good.

service_connect = ecs.ServiceConnectService(
                port_mapping_name=service_data['containerName'],
                discovery_name=service_data['containerName'],
                dns_name=service_data['containerName'],
                port=service_data['containerPort']                
        )

service = ecs.FargateService(self, "Service",
                    service_name=service_name, 
                    cluster=cluster, 
                    task_definition=task_def,                     
                    service_connect_configuration=ecs.ServiceConnectProps(services=[service_connect]))

ApplicationLoadBalancedFargateService looked like the perfect shortcut to create the client service, but it only has configuration options for Cloud Map Service Discovery. (https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_ecs_patterns/ApplicationLoadBalancedFargateService.html)

service = ecs_patterns.ApplicationLoadBalancedFargateService(self, "Service",
    cluster=cluster,
    task_definition=task_definition,
    cloud_map_options=ecs.CloudMapOptions(
        # Create A records - useful for AWSVPC network mode.
        dns_record_type=cloudmap.DnsRecordType.A
    ) 
    ....
)

It seems weird to have Service Discovery but not Service Connect, especially since FargateService supports both. Upon further investigation, Service Discovery is the only available option for other ECS Pattern constructs too. Am I missing something? Is there a reason why Service Connect configuration isn't included in ECS patterns?