ECS CloudMap - ServiceConnect : after update, ECS doesn't support having both CLoudMap and ServiceConnect

[ETisREAL]

Describe the bug

Hi, hope to find you well :)

After one of the recent updates, I am not able anymore to apply this kind of configuration

const qmmRedisService = new ecs.FargateService(this, `${props.STAGE}qmmRedisService`, {
            serviceName: `${props.STAGE}qmmRedisService`,
            cluster: qlashMainCluster,
            desiredCount: 1,
            securityGroups: [qmmRedisServiceSecurityGroup],
            taskDefinition: qmmRedisTaskDefinition,
            enableExecuteCommand: true,
            vpcSubnets: { subnetGroupName: props.qmmRedisSubnetGroupName },
            cloudMapOptions: {
                container: qmmRedisContainer,
                name: `${props.STAGE.toLowerCase()}_qmm_redis`,
                containerPort: 6379
            },
            serviceConnectConfiguration: {
                services: [{ portMappingName: `${props.STAGE.toLowerCase()}_qmm_redis` }]
            }
        })

Expected Behavior

This used to allow me to make use of the service connect monitoring, as well as resolving the DNS in a Peered VPC

Current Behavior

Now I can choose either a cloudmap configuration or a service connect one. With the first I have to sacrifice DNS resolution outside of the cluster, with the second I give up on extra monitoring

Reproduction Steps

NA

Possible Solution

Restoring this old functionality?

Additional Information/Context

No response

CDK CLI Version

2.88

Framework Version

No response

Node.js Version

v18.16

OS

Linux - Ubuntu

Language

Typescript

Language Version

No response

Other information

No response

[pahud]

cloudMapOptions creates CDK-managed cloudmap service which was the default behavior before service connect was introduced.

aws-cdk/packages/aws-cdk-lib/aws-ecs/lib/base/base-service.ts

Line 1107 in 4103e79

public enableCloudMap(options: CloudMapOptions): cloudmap.Service {

I think we should create a check, if serviceConnectConfiguration is provided, cloudMapOptions should be undefined.

[ETisREAL]

@pahud the issue of only having serviceConnect however is that it doesn't create the A record for the container, allowing other services to make use of cloudmap