Describe the bug

I had three CI pipelines fail with the following error starting today using both Go and Python cdk:

Runtime process exited abnormally: waitid: no child processes[Error at /***-***-scorer-ecs-stack] 
No load balancers found matching {"dummyValue":{"ipAddressType":"dualstack","loadBalancerArn":"arn:aws:elasticloadbalancing:us-west-2:123456789012:loadbalancer/network/my-load-balancer/50dc6c495c0c9188","loadBalancerCanonicalHostedZoneId":"Z3DZXE0EXAMPLE","loadBalancerDnsName":"my-load-balancer-1234567890.us-west-2.elb.amazonaws.com","securityGroupIds":["sg-1234"],"vpcId":"vpc-12345"},"account":"***","region":"us-east-1","loadBalancerTags":[{"key":"Name","value":"***-ds-apigtwy"}],"loadBalancerType":"network","lookupRoleArn":"arn:aws:iam::***:role/cdk-hnb659fds-lookup-role-***-us-east-1"}

[Error at /***-REX/***-REX-API-Gateway-V2] No load balancers found matching 
{"account":"***","region":"us-east-1","loadBalancerTags":[{"key":"Name","value":"***-ds-apigtwy"}],"loadBalancerType":"network","lookupRoleArn":"arn:aws:iam::***:role/cdk-hnb659fds-lookup-role-***-us-east-1"}

Pinning the aws-cdk CLI to npm install -g aws-cdk@2.166.0 resolved the issue in all pipelines. Perhaps could be related to the new Zonal Shift feature?

Regression Issue

Confirmed Regression

Last Known Working CDK Version

2.166.0

Expected Behavior

Looking up a still-existing Network Load Balancer by tag should work.

Current Behavior

The Network Load Balancer lookup fails to resolve.

Reproduction Steps

• Create a network load balancer in an account with a tag
• Attempt to look it up by tag

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.167.1

Framework Version

No response

Node.js Version

22

OS

Linux

Language

Python, Go

Language Version

Python 3.11 | Go 1.23.2

Other information

No response