Describe the bug

integ.multiple-application-load-balanced-ecs-service-idle-timeout

Error occurred: InvalidDomainNameException - example.com. is reserved by AWS!

integ.multiple-application-load-balanced-ecs-service

Behaviour: target groups pointing to port 90 always unhealthy

Try running sample image locally, port 90 actually doesn't work:
docker run -d -p 80:80 -p 90:90 amazon/amazon-ecs-sample:latest > curl http://localhost:90 FAIL
docker run -d -p 80:80 -p 90:80 amazon/amazon-ecs-sample:latest > curl http://localhost:90 WORK

Both tests are still using Launch Configuration > community member cannot run

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

No response

Expected Behavior

Integration tests should work seamlessly for anyone

Current Behavior

See description

Reproduction Steps

yarn integ test/aws-ecs-patterns/test/ec2/integ.multiple-application-load-balanced-ecs-service.js --force

Possible Solution

For both tests

• Integration test should migrate to Launch Template instead of Launch Configuration

integ.multiple-application-load-balanced-ecs-service-idle-timeout

Use your own cert pattern

integ.multiple-application-load-balanced-ecs-service

I can only think of 2 solutions. None of them are clean. Would need team advice:

• Modify nginx configuration in https://github.com/aws-samples/ecs-demo-php-simple-app to also expose port 90
• ApplicationTargetProps add support for hostPort/ Then we can hardcode hostPort (anti-pattern):

targetGroups: [
    {
      containerPort: 80,
      hostPort: 8080,
    },
    {
      containerPort: 90,
      hostPort: 8090,
      pathPattern: 'a/b/c',
      priority: 10,
    },
  ]

Additional Information/Context

No response

CDK CLI Version

main

Framework Version

No response

Node.js Version

v20.18.0

OS

Dev container

Language

TypeScript

Language Version

No response

Other information

No response